Can I create an INACTIVE record?
Views (484)
Arun Vinoth
11,615
Moderator
Like
Share
Report
As usual, this blogpost also originated from my learning/research/answer to a Stack overfow question :)
Often times, necessity comes and expect us to create an INACTIVE record in system. In such scenarios, we have to create the record in ACTIVE status and update it to INACTIVE in another update transaction.
Unfortunately we cannot create the INACTIVE record in one shot, it requires two DB transactions. One to create ACTIVE record and second one to deactivate it. This is by design.
Why is this needed?
Since the StateCode attribute metadata shows the isValidforCreate as No - we cannot set this attribute in Create transaction. Also when we set StatusCode only - we will face the error:
2 is not a valid status code for state code AccountState.Active on account
Because, statecode=0 is set as default by system, when you pass statuscode=2 in create payload - the platform validation kicks in and say this is invalid pair.
This was originally posted here.
Comments
-
Can I create an INACTIVE record?You can create an Inactive record by setting the inactive values in both statuscode and statecode of the target in a plugin step that kicks in the PreValidation or PreOperation
of message Create for the Table, thus avoiding a second transaction.
PreValidation is stage 10, PreOperation is Stage 20. PostOperation can be 40 or back in time also 50.
The transaction is committed into the Dataverse in stage 30.
Any change in the payload before stage 30, kicks in.
As far as I know, the only exception is the owner, which can't be changed in stage 20, but no problem if changed in stage 10.
*This post is locked for comments