Precisely Enterworks

I have two Digital Asset file name questions - one is a problem we're trying to solve and the other is just a curiosity.

First the curiosity - we use the custom uploader for suppliers to add their assets to their records that adds the datetime stamp to the file name.  I noticed the date is a month off and digging into it, realized that it codes January as 00 instead of 01, which causes all months to be one less than it should be.  Has anyone else noticed this discrepancy in the datetime added to file names?  I have not found anywhere else in EnterWorks that codes the dates this way.
Example - the date in the filename and the create date are highlighted.

Second - the problem.  Is there a way to prevent files from uploading and display an error message if the files contain certain characters?  I've found the callout "No Invalid Characters" that I can use that will show an error on the file name, but it doesn't prevent the file from uploading or a DamLink record from being created. We're trying to prevent suppliers from uploading files that we can't use without completely renaming the file.  We're specifically trying to prevent inclusion of spaces, commas and hashtags/number signs, and non-English letters.  We're trying to educate suppliers, but enforcing naming conventions is an uphill battle.  Does anyone have a work-around?  I've also been experimenting with other bulk callout rules that would cause an Severe Error on our Digital Assets tab, preventing the supplier from sending a new record to workflow, but that's a bit more out of my depth at the moment. 

Lindsey,

Are you referring to the custom action that allows for files to be uploaded and linked to the record being edited?  I have not seen a date format resulting in a zero-based month being specified.  I suggest you attach the JSP file that is configured for this upload to a support ticket with the details so it can be reviewed.

If suppliers are uploading files using the same method, the JSP can be modified to reject a selected file as having an invalid name or it could strip out the invalid characters.  This would be preferred over having some validation rule flag file names with those characters as the latter doesn't prevent the files from being submitted whereas the validation on upload would provide immediate feedback to the supplier that they need to change the name of the file.  This approach has a much better chance of getting the suppliers to change their behavior.

I have two Digital Asset file name questions - one is a problem we're trying to solve and the other is just a curiosity.

First the curiosity - we use the custom uploader for suppliers to add their assets to their records that adds the datetime stamp to the file name.  I noticed the date is a month off and digging into it, realized that it codes January as 00 instead of 01, which causes all months to be one less than it should be.  Has anyone else noticed this discrepancy in the datetime added to file names?  I have not found anywhere else in EnterWorks that codes the dates this way.
Example - the date in the filename and the create date are highlighted.

Second - the problem.  Is there a way to prevent files from uploading and display an error message if the files contain certain characters?  I've found the callout "No Invalid Characters" that I can use that will show an error on the file name, but it doesn't prevent the file from uploading or a DamLink record from being created. We're trying to prevent suppliers from uploading files that we can't use without completely renaming the file.  We're specifically trying to prevent inclusion of spaces, commas and hashtags/number signs, and non-English letters.  We're trying to educate suppliers, but enforcing naming conventions is an uphill battle.  Does anyone have a work-around?  I've also been experimenting with other bulk callout rules that would cause an Severe Error on our Digital Assets tab, preventing the supplier from sending a new record to workflow, but that's a bit more out of my depth at the moment. 

I have two Digital Asset file name questions - one is a problem we're trying to solve and the other is just a curiosity.

First the curiosity - we use the custom uploader for suppliers to add their assets to their records that adds the datetime stamp to the file name.  I noticed the date is a month off and digging into it, realized that it codes January as 00 instead of 01, which causes all months to be one less than it should be.  Has anyone else noticed this discrepancy in the datetime added to file names?  I have not found anywhere else in EnterWorks that codes the dates this way.
Example - the date in the filename and the create date are highlighted.

Second - the problem.  Is there a way to prevent files from uploading and display an error message if the files contain certain characters?  I've found the callout "No Invalid Characters" that I can use that will show an error on the file name, but it doesn't prevent the file from uploading or a DamLink record from being created. We're trying to prevent suppliers from uploading files that we can't use without completely renaming the file.  We're specifically trying to prevent inclusion of spaces, commas and hashtags/number signs, and non-English letters.  We're trying to educate suppliers, but enforcing naming conventions is an uphill battle.  Does anyone have a work-around?  I've also been experimenting with other bulk callout rules that would cause an Severe Error on our Digital Assets tab, preventing the supplier from sending a new record to workflow, but that's a bit more out of my depth at the moment.