Sharepoint

[mrusso1995]

I have 3 lists in Sharepoint
2 of those lists get synced into the 3rd list.
I am creating the items in those 2 lists, but for some reason, the 3rd lists is not syncing everything in or it is getting deleted when I add a new item into one of the 2 lists.

[mrusso1995]

@abm 

[Anonymous]

Please provide screenshots of your flow to help anyone able to provide assistance understand what the flow is actually doing.

Consider reading this article on how to write a good forum post.

thanks,

Kyle

[mrusso1995]

[mrusso1995]

Hi, it definitely have something to do with the Number ID's since I am using two different list to merge into one list, so the number ID's are overriding each other. 

[Anonymous]

@mrusso1995 ,

couple of questions,

do you have a flow for each of the two lists you actively manage? the flow you shared will only run when the "Alton Source Client Review" list is modified. If the "Database" list is the third "merged" list, then nothing is currently happening when your second list is modified.

as far as the ID issue is concerned, you can consider modifying the ID's as they flow into the third list by appending one of two unique numbers to the beginning of the ID coming out of the original list.

For example use 1 for the first list and 2 for the second list, so when the list item is created in the third list, the records from lists one and two that have ID 1001, would have IDs 11001 and 21001, respectively, when created in the third list.

thanks,

Kyle

[mrusso1995]

Yes I have two different flows, one for Alton and one for Mike, they follow the same steps except the change from where the list items will come from but still both going into the Database.
How would I do this then in terms of how the flow will look, I created two different columns to see if I could do one ID for NumberID - DC (Mikes) and one ID for NumberID - DB (Alton) @Anonymous 

[Anonymous]

@mrusso1995 ,

On second look, the ID's shouldn't be your issue, as the Database list is creating unique IDs as you create records in that list. It looks like you are comparing the ID from list one to the ID in list three thinking that they will refer to the same record, they don't. the ID is not something you can change, notice that it is not a field that you can set when creating a new record.

it looks like you're determining whether a record needs to be updated or created based on whether or not the length of a certain field is 0. Can you share that full expression? 

The only way I can think, off the top of my head, to link a database record back to records in the two "feeder" lists, is to have a column in each feeder list that stores the ID of the associated database record.

otherwise, you may need a separate key identifier that is common between the three lists.

this one seems pretty tricky.

[mrusso1995]

The length condition is length(outputs('Get_Items')?['body/value'])

I understand you cannot change the ID but how would the flow look like if I make the change ?

@Anonymous 

[Anonymous]

@mrusso1995,

length(outputs('Get_Items')?['body/value'])

When is that ever going to evaluate as true? I think that will only have a length of 0 when there are no items in the "Database" list at all.

As far as your question is concerned:

You could add another "update item" after creating a new Item in "Database" updating the "List One/Two" item to reflect the ID of the newly created "Database" item.

however, to avoid and endless looping Flow (since updating that item would trigger the flow again) you would want to check if that "Database Item ID" field is empty first.

thanks,

Kyle

[mrusso1995]

Okay so how would my flow look like doing that as I do not want duplicates or looping .

[Anonymous]

In your first "Get Items", you should change the filter to filter based on that new column in the Alton list. Then the first Condition can check to see if anything is returned (I see now how nothing would be returned in get Items since you are using a filter query) and create or update as necessary.

For populating that new column:

I would use a condition to check to see if that new column (for the "Database" record ID) is empty in the Alton list.

since you already have that record's ID from the Alton list (from the trigger; since that was the record that started the flow in the first place), you can put a condition in under the "create item" action in the "yes" side of your first condition, pass in the Dynamic Content for this new column and see if it equals the expression "null()" (make sure you put it in as an expression, not just type it into the field).

in the "yes" side to this second condition, add an "update item" action and set the value of the new column to the ID of the current Database record (I think in your flow you've already passed it into a Compose, so you could use the output from that).

in the "no" side of this second condition, do nothing.

this way, if that field(column) is already populated, the record will not be updated, and it will not trigger the flow to run again.

that is what I think your flow should look like.

Kyle

[abm]

Hi @mrusso1995 

@Anonymous  I know you are trying to help @mrusso1995 . This question is a follow up of another post I did helped @mrusso1995 a while ago. Earlier I had a screen share with @mrusso1995 

The issue was two different lists trying to sync into another single list. The mistake was it was using the ID to Create/Update/Delete. Since its coming from two different lists the internal ID values generated are same at some cases hence the sync had issues. According to @mrusso1995  title value is always unique between the two lists so all the filters are modified to look the title instead of the id. This has resolved the issue.

@Anonymous  really appreciate your help in this. Have a good weekend.

Thanks

[Anonymous]

@abm,

Glad to hear! Thank you for your expertise!!

Have a great one!

Kyle

[abm]

Hi @mrusso1995 

If your problem has solved, please go ahead and mark the post as solved by clicking “Accept as Solution” so that this thread will be marked for other users to easily identify!

Thanks