Unanswered

Avoid duplicate records in Dataverse for Teams Table

(0) Share

Report

Posted on by bwingate

Hello,

I have been tasked with creating a case screening system using Dataverse for Teams and Power Apps. My Power App should allow the user to upload a properly formatted Excel workbook, parse the data via Power Automate, and upload the records to various tables within the Dataverse for Teams tables the Power App utilizes as a data source. The issue: duplicates. Dataverse for Teams does not allow for secondary keys which would prevent the uploading of duplicates by Power Automate when a user uploads and Excel file.

I am finding it impossible to check the existing records for duplicates and then upload only the cases that are new in the incoming file. I have two properties I can work with to limit the records from a List rows in table call to Dataverse - case number and case location.

First step in retrieving existing case

I have successfully done a List rows in table with an OData filter for both of these. However, I have followed almost every post I can find out there on how to then list only the non-duplicate cases from the incoming JSON data that the Excel file generates.How can I exclude existing cases listed in the incoming data?

Has anyone been able to ensure duplicate values are not created in Dataverse for Teams in this type of scenario and if so, how?

Thank you in advance for any advice.

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

Sort by

abm abm 32,985 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @bwingate

Who generates the case number? Can't you auto generate it each time. Could you please explain how case number gets duplicated?

Thanks

Was this reply helpful? Yes No
bwingate 4 on at

Like (1)

Report
Copy link

Link copied!

Hi abm,
The case numbers are generated in a separate system and it is essential that they stay the same so as to be able to identify them for processing in the other system. So, I cannot auto generate them.

The scenario is this: We receive an XLS with case information including the case number from the entity who initially creates the case. The Power App ingests these cases (via the Flow), for additional screening, and then a user re-inputs the final screening information manually into another system.

Since multiple users may accidentally upload the same file or an XLS with the same case I want to make sure they are not duplicated.

Does this make sense?

Was this reply helpful? Yes No
abm abm 32,985 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @bwingate

Yes it does make sense. Thanks for the detailed reply. I can see from your screenshot you have added an IF condition to check whether the case number exists or not? That make perfect sense to me. I believe down the down the line based on that condition you are creating the case.

Thanks

Was this reply helpful? Yes No