Plugin Diff Pre-validation, pre- operation, post-operation stages

Pre- validation means your plugin will run before the form is validated.

Pre- operation is after validation and before the values are saved to the database.

Post- operation is your plugin will run after the values have been inserted or changed on the database.


Realtime example :



saved, it is the first layer, usually used for validation, but not many people use this, usually will just use pre-operation.

2. Pre-Operation: is also before the record created, not yet database transaction committed.

This is usually used to modify attribute value by system (logic code), validation as well.

Any changes of attribute in the pre-validation would be dismissed if you modify the attribute from this stage.

Since mentioned before, this is not yet created, so, there is no ID created at this point.

3. Post-Operation: is after the record created, database transaction committed, and you would get the GUID.

You cant change the value of the record in this stage since already committed, but you can take next action, what's next you do for this record or another action.

Example: Want to assign this record to another owner (reason why you put on Post is because you need GUID), share to another team, send email as notification, create task or anything you need reference to this record, because you need this record created first.

 

Comments

Post a Comment

Popular posts from this blog

Power Automate compose vs variable

  Variable Compose Variables hold different types of data types like string, boolean array, etc, to validate what we give in terms of our data. If the data doesn’t match the data types it will give an error. Compose action is typeless, which means it is very flexible, we can provide any type of data(we can give XML, JSON, etc) as an input. Variables can be set many times, which means we can set it, reset it at any point of our flow, as per our requirement. Compose only set once, which means compose doesn’t have the update function It can be grouped together under the variable heading, which means when we access the variable from the dynamic content. It was very clearly visible in the dynamic content because we can see the name of a variable, and also make it easy to identify what the variable is in dynamic content and what variable I want to use. Compose are not grouped, which means we give some data as input and it will return some data as output. So in dynamic content, we can onl...
Read more

Update record when checkbox checked using JavaScript and save d365

On checkbox on change following function called -------------------------------------------------------------------- function IsClientDisease(executionContext) {     debugger;     var formContext = executionContext.getFormContext();     var selectedValues = formContext.getAttribute("ecl_isclientdisease").getValue();     var id = formContext.data.entity.getId().replace("{", "").replace("}", "");     if (selectedValues == 1) {         var fetchbooking = "<fetch version='1.0' output-format='xml-platform' mapping='logical' distinct='true'>" +             "  <entity name='contact'>" +             "    <attribute name='fullname' />" +             "    <attribute name='telephone1' />" +             "    <attribute name='contactid' />" +  ...
Read more

Power pages custom button add in gried

  $(document).ready(function () {     // Loop through table rows after entity list loads     $(".entity-grid .view-grid table tbody tr").each(function () {         var recordId = $(this).attr("data-id"); // row GUID         if (recordId) {             var viewBtn = `<button class="btn btn-primary btn-sm view-btn"                              onclick="openDetails('${recordId}')">View</button>`;             $(this).find("td:last").append(viewBtn); // put button in last column         }     }); }); function openDetails(id) {     // Replace with your detail page URL     var detailPageUrl = "/bankaccount-details/";     window.location.href = detailPageUrl + "?id=" + id; }
Read more