It's possible to update inactive entities with CrmServiceClient. Is this a bug?

(0) Share

Report

Posted on by krombipils

Hi,

I'm once again evaluating DataVerse/Power Apps and I wonder if the following behaviour is a bug or by design:

As soon as an entity is in an inactive state, it cannot be changed via forms. This is the desired behaviour. But when using an Update request via the CrmServiceClient, it is still possible to perform changes.

Actually I don't like this behaviour. I think it should be possible to prevent all changes to an entity.

I know it is possible to lock fields with Business Rules, but there is no 'lock all fields' command, therefore it is really annoying. Did I missed something?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (5)

Answers (1)

krombipils 19 on at

Like (0)

Report
Copy link

Link copied!

I guess I found the answer to my question (question is related to business rules, but obviously the same is true for statuses): Locked-field-using-business-rules-is-getting-updated-through-API/td-p/564170

I wonder if I am the only one who does not like this behaviour.

Was this reply helpful? Yes No
Verified answer

EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @krombipils,

Good to know you found your solution. To supplement, apart from Case (incident) entity/table you can still update inactive records via the APIs/SDK, Power Automate, Excel import, workflows, etc. Business rules are mainly used for front-end (i.e forms) logic so you won't be able to unlock inactive records, however you can lock specific fields with business rules.

Hope this helps...

Was this reply helpful? Yes No
Rudylar 18 on at

Like (0)

Report
Copy link

Link copied!

To bounce on this topic, my use case (and I guess a pretty standard one) is that INACTIVE entities should NOT be modified (at least headers, not necessary lines). I am being said that this cascading setting is not included in Dynamics 365.

For instance, if an Account's owner changes, we don't want won opportunities (inactive) to have their owners changed too. But changing active opportunities could be a requirement.

Distinguishing between active and inactive when setting up relationship behavior should be possible.
Anybody knows?

Was this reply helpful? Yes No
MichaelFP 1,886 Moderator on at

Like (1)

Report
Copy link

Link copied!

@Rudylar for your scenario i believe that the best is to use an plugin that will validate if the opportunity state is won or inactive, and if it is using pre-image change back the data that you want to keep.

Was this reply helpful? Yes No
EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @Rudylar,
A bit like @Michaelfp mentioned, the best way to prevent changes on inactive records would be with synchronous pre-operation plugin. If the status (statecode) is inactive (value 1), simply throw an InvalidPluginExecutionException, and that's it.
Note: InvalidPluginExecutionException is the only supported custom exception that can be thrown

Hope this helps!

Was this reply helpful? Yes No