Re: avoiding duplicate records in dataverse custom tables
Hi @GuidoPreite @bipinshan
Both scenarios fit for me but i see i will have an issue let me describe:
in a table Components i store Project name, Component name, Component qty
In table Transactions i register what was done with the certain component so it looks liek this
Project name:Project1
Component name: A001
Component qty:1
Status: completed
But it might happen that i have the total qty of Component name A001 2psc
then if user registers the completed qty in separate records 1 by 1 this A001 and i enable duplicate detection rule it will not allow him to enter this another missing 1 psc from total 2
What would you suggest in this case?