Tip #486: Don’t hard code currency in workflows

If you have a workflow dealing with the entities that include money fields, avoid setting explicit currency. Instead, try to infer the currency from the related records.

Bad currency workflowGood currency workflow

For mere mortals, it’s just a bad practice, for ISVs, it’s definitely a case of spießrutenlaufen.

Why? Because if you activate your workflow and add it to a solution, then importing your solution to any CRM organization that does not use MMDDYYYY as their date format (and therefore will opt for their own currency), will complete with the warnings and the workflow on the target system will be deactivated.

Solution import warning
US currency problem

Tweet about this on TwitterShare on Facebook0Share on Google+0

Leave a Reply

Your email address will not be published. Required fields are marked *