Hello;
I’m generalizing the issue to a simple fruit stand to isolate the problem… Further down in my explanation I get to the Power Automate part of my question...
Suppose there is a fruit stand that sells fruits. Whenever the fruit stand makes a sale, they input it into their Power Platform app. The app is a combination of a Power App and a dataverse “database”.
This is what the app looks like…
This is what the backend dataverse table looks like…
Dataverse requires a [Name] column that must be filled in with a value. At the start of the project, I set this datatype to “Autonumber” with a seed value of 1000. I figured this column could serve as a unique ID.
At the beginning of this app’s life, it was using a “Patch” statement to put the data in the dataverse table.
After a couple months in use however, the app now needs to input the data into the dataverse table a different way. The app needs to pass the data to a Power Automate flow, and the flow will use the “Add a new row” action to add a row to the dataverse table. No more patch statements. So, I set this up…
Here is where the challenge arises:
When adding a row to a dataverse table using the “Add a new row” action in Power Automate, a value is required for the [Name] column. However, I already set this value as an “Autonumber” datatype, because I originally intended this column to serve as a unique ID for each row in the table. If I input a value into this column (for example, the constant 1), then I will get the following results:
Here are my questions:
Is there a way to work around this specific problem using the “Add a new row” action?
Should the [Name] column be used as an Autonumber ID? Or something else?
Thank you!
