Hi All,
I was wondering if there is a standard, best practices method for configuring lookup fields within a workflow when deploying the solution to another server? I am often finding that when I move a solution from development to production, whenever I have a lookup field in my workflow that is not dynamically set (i.e. I have to explicitly set the value from a list of values from another entity), I have to reset that value in production.
For example, I have a check condition that checks to see if the value set in the field on the primary entity is equal to a specific value in another entity that contains a list of valid values (this is not an Option Set due to other business requirements, so it is a "configuration" entity that stores these different values). When I push this workflow to production, I have to reset the check condition by clicking on the value of the "configuration" entity I'm comparing against so that the value gets refreshed. It makes sense to me as behind the scenes the GUID of the lookup value needs to be the production GUID and not the one that came over from my development environment.
So what I was wondering was if there was any way to handle for this automatically? I thought that maybe the CRM Package Deployer would handle for this, but I've not used it yet. It seems to me that this would be a very common scenario and I'm missing something or not doing something properly in my deployment steps, so any help here would be appreciated.
Thanks.
*This post is locked for comments
I have the same question (0)
