Applies to Product - Microsoft Dataverse
What’s happening?
The customer observed that an end user was able to successfully insert a row into a Dataverse table using an Automate cloud flow, even when the ID field was left empty. This raises concerns about the potential for frequent occurrences of inserting records with empty IDs.
The customer observed that an end user was able to successfully insert a row into a Dataverse table using an Automate cloud flow, even when the ID field was left empty. This raises concerns about the potential for frequent occurrences of inserting records with empty IDs.
Reason:
By design.
By design.
Resolution:
To prevent the insertion of records with empty IDs, the customer should implement a validation mechanism in the Automate cloud flow to ensure that the primary key is always provided before attempting to insert a record. If the primary key is not supplied, the flow should either prompt the user for a valid ID or prevent the insertion altogether.
To prevent the insertion of records with empty IDs, the customer should implement a validation mechanism in the Automate cloud flow to ensure that the primary key is always provided before attempting to insert a record. If the primary key is not supplied, the flow should either prompt the user for a valid ID or prevent the insertion altogether.