Hi Eickhel, thanks very much for this video. Instead of querying the dataverse table and creating new queries it is possible to select a key in the 'Map Tables' step. Dataflow will pick up on the key and for all the rows to be imported it will use the key to identify existing rows. The existing rows will be updated instead of duplicate rows being created.
Thank you for this tipp. I just implemented it. A note on this: For the mapping column, you need a value of the type "string formatted like a GUID" in your input. I first had to create one in the powerquery, which I achieved with a custom column using the formula: Guid.From(Text.Combine({[PID], "00000000000000000000000"})), PID is my "ID" field from the data source.
So, when using keys, already existing rows are updated, right? I was concerned that when using keys, rows that already exist in Dataverse might be completely skipped, and I don’t want that because some rows may have fields that need to be updated. For example invoices - if amount of the invoice is changed (lets say Amount column is not used as part of the KEY) then dataflow will update that row instead of skipping it, right?
Great content with a really practical example. Finally I can see MS is bring Power BI / Power Query into power apps. I am hoping the dataflow is shared across power bi as well so as to have a single instance.
Could you show how to migrate relationships - e.g. Parent account of contact and primary contact for account, because Dataflow seems kind of lackluster in that regard?
Hi Eickhel, thanks very much for this video. Instead of querying the dataverse table and creating new queries it is possible to select a key in the 'Map Tables' step. Dataflow will pick up on the key and for all the rows to be imported it will use the key to identify existing rows. The existing rows will be updated instead of duplicate rows being created.
Thank you for this tipp. I just implemented it. A note on this: For the mapping column, you need a value of the type "string formatted like a GUID" in your input. I first had to create one in the powerquery, which I achieved with a custom column using the formula: Guid.From(Text.Combine({[PID], "00000000000000000000000"})), PID is my "ID" field from the data source.
So, when using keys, already existing rows are updated, right? I was concerned that when using keys, rows that already exist in Dataverse might be completely skipped, and I don’t want that because some rows may have fields that need to be updated. For example invoices - if amount of the invoice is changed (lets say Amount column is not used as part of the KEY) then dataflow will update that row instead of skipping it, right?
Great content with a really practical example. Finally I can see MS is bring Power BI / Power Query into power apps. I am hoping the dataflow is shared across power bi as well so as to have a single instance.
Very nice and useful! How the complex SharePoint field's data will be synced to Dataverse table?
very nice tutorial. Will this also work when there is just an update in Sharepoint, so no new record but dataverse need to be updated?
Super useful. Thanks.
Could you show how to migrate relationships - e.g. Parent account of contact and primary contact for account, because Dataflow seems kind of lackluster in that regard?
Can we use it on lookup o choice columns ?