I have an entity called UserBank that has not been able to write new records for the past few months. This is true while trying to do it in the Excel add-in and within an app. I don't exactly understand the error:
Error Publishing Row Details: A row created in data set UserBank_ was not published. Error message: 'Write failed for table row of type 'RTSUserBank_'.
Infolog: Error: Cannot create a record in RTSUserBank__Table (UserBank). The record already exists..'
It says the record already exists, but it's a new record so I don't see the problem.
Can I get some help on this?
Solved! Go to Solution.
I'm glad to hear it. We have a known issue at the moment with our autonumbers - and there are scenarios where you can get into a situation where your next number to be issued, as already been used - this is why you get an error because the unique value has already be used once in your entity.
We need to handle this more gracefully, and progress the numbers, or allow you to control the next number - we are working on both of these to improve autonumber in the future.
Thanks again for reaching out,
Hi @mr-dang,
Would you please share more details about the mentioned field "RTSUserBank_ ", including its data type, and the field property?
The error message you posted seems to be mostly related with the field property restriction.
Please share the data types in an example, I will check and see if I could reproduce this.
Regards,
Michael
Hi @v-micsh-msft,
I seem to be having the same issue. This appears to have happened while I have been absent from the office - no one else monitors my app, so nothing has been changed.
Hopefully you can assist?
I have attached screenshots below with my error message (same as @mr-dang, RTS...) and the property field settings for each data field.
Thanks,
James
Hi Mr Dang / James,
If you could confirm that your entities have a Primary Key field that is of type Auto number? If so, it's most likely there is an error with the autonumber that is what's causing the potential duplicate error.
If that's the case - if you could send me some information in a private message here - we can get the team to look at your environments. If you could please go to web.powerapps.com and select your environment, then open the list of entities, select the Account entity. Once you are on the Account entity field list, copy the full URL in your browser.
If you could send that to me along with the name of your entities - we will have a look at it for you.
Thanks,
Hi Mr Dang,
Your environment should be updated - please retest and let me know if you're unblocked.
Thanks,
Confirmed:
My entity is working!
I'm curious what was happening with it?
Thank you very much!
I'm glad to hear it. We have a known issue at the moment with our autonumbers - and there are scenarios where you can get into a situation where your next number to be issued, as already been used - this is why you get an error because the unique value has already be used once in your entity.
We need to handle this more gracefully, and progress the numbers, or allow you to control the next number - we are working on both of these to improve autonumber in the future.
Thanks again for reaching out,
Hello,
Am also getting the same error while submitting the form for an entity while creating new record ...
please help me out
Hi Renuka,
Sorry to hear you're having problems. If you could send me some information in a private message here - we can get the team to look at your environments. If you could please go to web.powerapps.com and select your environment, then open the list of entities, select the Account entity. Once you are on the Account entity field list, copy the full URL in your browser.
If you could send that to me along with the name of your entities - we will have a look at it for you.
Hi.
I have this problem now. I tried to create a new Common Data service Entity. I get the same error. Is it something wrong with the Primary ID?
RecordId is automatically created but I can see that the checkbox Unique is not checked.
I can see this problem is from 2017. Surely you have a solution for this
Thanks in Advanced.
User | Count |
---|---|
135 | |
133 | |
79 | |
75 | |
71 |
User | Count |
---|---|
210 | |
201 | |
69 | |
62 | |
53 |