Posts

Showing posts from February, 2023

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 nex...

plugin registration tool download link

https://xrm.tools/SDK

Power automate Expand Query

Image
Video :  Expand query  

What is power query D365 ?

Image
Power Query is a data transformation and data preparation engine. Power Query comes with a graphical interface for getting data from sources and a Power Query Editor for applying transformations. Because the engine is available in many products and services, the destination where the data will be stored depends on where Power Query was used. Using Power Query, you can perform the extract, transform, and load (ETL) processing of data. How Power Query helps with data acquisition Business users spend up to 80 percent of their time on data preparation, which delays the work of analysis and decision-making. Several challenges contribute to this situation, and Power Query helps address many of them. Existing challenge How does Power Query help? Finding and connecting to data is too difficult Power Query enables connectivity to a wide range of data sources, including data of all sizes and shapes. Experiences for data connectivity are too fragmented Consistency of experience, and parity of...

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...

Microsoft Flow vs Microsoft Dynamics CRM Workflow

Image