Business Rule Not Working Across Environments

(1) Share

Report

Posted on by Weir311

I have a business rule for cases that gets triggered when a specific Account is selected. This Account existed in production, but not my test environment so I manually created it in test, then completed the rule. It worked fine in test, so I exported the solution and moved it into production where it stopped working. While troubleshooting I modified the rule in production and selected the account again, and the rule started working.

My suspicion is the rule is tied to the GUID of the account, not just the account name, and since I manually created the account in dev it has a different GUID than the account in production which is breaking the rule. To test I changed the name of the existing account the rule uses and sure enough the rule still worked after the change. Does this sound like it's working as expected? If so, any suggestions on how should proceed with this? My concern is that if the rule gets included in future packages it will stop working again until it gets manually created in the production environment.

Any assistance or suggestions would be appreciated.

Thanks!

Bob

I have the same question (0)

All responses (5)

Answers (3)

Verified answer

empath-e CRM 1,136 on at

Like (0)

Report
Copy link

Link copied!

Hi Bob,

I thought I would test this one myself and sure enough it does use the GUID and not the value entered. I thought I would test the same scenario but within a Workflow and it is the same, it is looking for the record GUID. I assume this is by design and not a bug? I do work with another CRM solution and this works on record value and not GUID which is why I was interested in testing this myself.

Was this reply helpful? Yes No
empath-e CRM 1,136 on at

Like (0)

Report
Copy link

Link copied!

Thinking about it, I assume this is to prevent duplicates being returned within the processes when triggered

Was this reply helpful? Yes No
Verified answer

Bipin D365 28,985 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi,

One way to permanently fix this issue is to create account in dev with production guid using oob import and sync this account record in all lower instances.

You can also use configuration migration tool to create account record with same guid from production to dev

Was this reply helpful? Yes No
Verified answer

Inogic 748 on at

Like (1)

Report
Copy link

Link copied!

Hi,

Yes, I can confirm that it is working as expected. When your IF condition is “equal to” a specific lookup field value, the GUID of the lookup record will be “hard-coded” into the rule.

As a workaround we can use “begins with” operator rather than an “equals”, to compare Lookup value with Text as shown below:

Note: If there are multiple records exists with the same name, then the logic might not work as expected.

OR

You must keep Guids same in all environments. You can use migration utility tool to deploy your reference data.

Please find below referenced link to download the tool:

https://learn.microsoft.com/en-us/power-apps/developer/data-platform/download-tools-nuget

OR

Try not to hard code anything in the business rule. You can implement the logic using Script.

Please find below referenced link for client API object model that can be used with JavaScript libraries:

https://learn.microsoft.com/en-us/power-apps/developer/model-driven-apps/clientapi/reference

Thanks!

Was this reply helpful? Yes No
Suggested answer

Weir311 7 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the responses

Was this reply helpful? Yes No