I have some tables where the primary name column has to be generated to be human-readable and a useful encapsulation. e.g. A Student table has first and last name columns. The name column gets set to 'first last'.
I have experimented with different methods of updating the name column, but wonder which is considered best practice.
Hide the name column on the entry form. Update the column with an OnSave event. (I can imagine this being more difficult if more forms are added, or an editable grid is used.)
Use a business rule to Set Value.
Use a cloud flow to Update a Dataverse Row on addition/modification/deletion
What is considered best practice? What are the possible consequences or pitfalls to avoid?
I would recommend to create a plugin in Dataverse whenever a record is created and update. In that case you will cover all scenarios: Forms, Excel Import, Sdk, javascript. No matter the place that you apply the create or the update the plugin will run for you to fill primary field of the table.
If my answer helped you, please give me a thumbs up (👍). If solve your question please mark as answer ✔️. This is help the community.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
2
Share
Report
All responses (
Answers (
