Importing tables that relate to another table (in a parent/child style relationship)

(0) Share

Report

Posted on by alstearns

Hello All,

I'm very new to Power Apps, specifically model driven apps.

I've imported all of our "Accounts" from salesforce to an Account table in the dataverse.

Now I want to import all of our "Opportunities" to a "jobs" table i've built in the dataverse.

How do I import all of these "Opportunities" into the "jobs" table and have them show under the "related" tab of the Accounts?

1 Account to be related to many "Jobs" and "appointments"

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (9)

Answers (0)

EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report

Hi @alstearns,

This should be pretty simple. First ensure you have a lookup column on Jobs that points to the Account table. This will display out-of-the-box the Jobs on the Related tab of the Account form. Then, import the opportunities/jobs in the Jobs table the same way you did for Accounts but ensure you see the Account column on Jobs, you can use the Primary Column value of the Accounts which is the Account Name.
Hope this helps!

Was this reply helpful? Yes No
alstearns 11 on at

Like (0)

Report

Hi Eric,

Thank you and sorry for the delayed response, had some time off for the new year.

I do have "lookup" column on the "Jobs" Table that points to the Account Table.

Where im getting lost is in the import. That Lookup field that points at the account doesnt show up as a mappable field when importing. I can easily have the the exact account name on the source record in salesforce (I've already done that), but I dont know what column to map to that account name from the source too when that lookup field doesnt show up in mapping in the destination columns. Do I need to run a flow or something to migrate that account name data from a separate account name field on the job table to the account lookup column?

What do you mean by "ensure you see the Account Column on jobs", is there a step to get that account lookup field to display in mapping that I am missing?

Was this reply helpful? Yes No
Drew Poggemann 9,287 Most Valuable Professional on at

Like (1)

Report
Hi @alstearns ,

Please review and let me know if this isn't your situation...

On your Jobs table you should have a field that is a Lookup to the Account table right? Example field would be Account Name

When you import the Opportunities from Salesforce into the Jobs table, one of the columns that you should be able to import is the "Account Name" column.

If you have imported your Accounts already then when you import the Jobs and populate the Account Name with the name it will automatically create the relationship to the related Account table. Note - This requires the Account Name to be unique in the Account table or the record will fail to import. If you have duplicate values you will need to map to another field that would be unique (example: Account Number) field. This can be done through the data import wizard to map to an alternate field in the Account table https://arcticit.com/getting-the-most-out-of-the-dynamics-365-data-import-wizard/

Was this reply helpful? Yes No
alstearns 11 on at

Like (0)

Report
Hi Drew,

On your Jobs table you should have a field that is a Lookup to the Account table right? Example field would be Account Name
I DO have an data type "lookup" field on the jobs table that points to the accounts name
When you import the Opportunities from Salesforce into the Jobs table, one of the columns that you should be able to import is the "Account Name" column.
NO lookup fields show up to map at all when im in the import mapping fields to an existing table screens, including that specific lookup to the account column.
If you have imported your Accounts already then when you import the Jobs and populate the Account Name with the name it will automatically create the relationship to the related Account table. Note - This requires the Account Name to be unique in the Account table or the record will fail to import. If you have duplicate values you will need to map to another field that would be unique (example: Account Number) field. This can be done through the data import wizard to map to an alternate field in the Account table https://arcticit.com/getting-the-most-out-of-the-dynamics-365-data-import-wizard/
I have already imported ALL the Accounts, however with a database of 200k+ I cant say for sure that there isnt going to be two different accounts with the same name so Account Number may be the better data set to use.
I have been doing imports through Power Apps-Table-selecting "Import" at the top button bar -Choose Data Source (selecting Salesforce Objects)-Connection Settings Screen (hitting next, I have played around with "include relationship columns" and didn't see a change or that lookup field show up, Choose Data Screen (selecting the Opportunity object from the list)-from there are the columns to map to the fields in salesforce.
How does the lookup column that looks at the account relate the two tables if i cannot map the account name or number from salesforce into it?
If I go with the Account Number, how do I get the lookup field to "look" at the account number data that's on the Account table records I've already imported and match it with the account number (lookup field) on the Job/Opportunity table.
Do I need to delete the current account table and all the data imported and do a new account table with "Account Number" as the Primary Column since the current one has Account Name as the Primary Column?

Was this reply helpful? Yes No
stefan68 23 on at

Like (0)

Report

i am facing the same issue, having salesforce accounts & opportunities imported in dataverse and trying to build the relationship between Id (accounts) and AccountId (Opportunities).
Did you find any solution for that problem?

Was this reply helpful? Yes No
alstearns 11 on at

Like (0)

Report

I ended up using the unique numbers on the salesforce entities (Accounts and Opps) and created the lookup fields (columns) in the dataverse pointing to them on the parent record. I added a couple subgrid's on my accounts, one on two different tabs showing only related too opps. and imported my opps separated by the record type (our two different job types) in the Power Query Import so the existed as separate tables in the dataverse. This also ensures my users are creating the correct type of opportunities for the accounts moving forward, since they create new opps from these same Subgrids.

I was never able to get all of our appointments to sync to opps in import, finding this to be due to countless user errors over the years in salesforce relating appts to accounts or not relating them at all if they made them from the wrong entity, so it was not always that one entity from salesforce that the lookup field on the dataverse was looking for, causing the import to always fail. Instead I added the lookup field on the appointments and elected to import the related unique id and put it on the appointment form right by the lookup so it can be referenced in cases of service work, when past appointments need to be references in the dataverse search. The user can than link the appointment to the opp manually as they work through things as they come up naturally. Luckily the dataverse search, if configured correctly, makes finding things easy on the user side.

The import of data was the most stressful, grinding wheels aspect of my power apps experience, i had to do it many times with it failing before i could get it to take.

ALSO, important step that is easy to overlook, your opportunities will fail if they dont have a parent account, so always make sure your account important is done first and that nobody is creating new accounts and opps while you are doing the import. So if your accounts are importing, and by the time you are importing opps, someone has added a new account and opp in salesforce (the account being missed from the account import) your opportunity import will fail, since it will be pointing to an account record in the lookup field that does not exist in the dataverse.

Was this reply helpful? Yes No
stefan68 23 on at

Like (0)

Report

Hi, thanks a lot for you valuable hints, I will go through the steps this week. I have also added subgrids to show the related opportunities for an account.
I just stumbled across one sentence.. "The user can than link the appointment to the opp manually ..."

Does that mean you need to do that manually for all accounts? This is what I actually wanted to avoid, simply use the sfdc ID (Acct table) and AccountID (Opportunity table) and auto-relate the records, so that opps show up in the subgrid of an account.
As I said I will go through the steps and check the outcome.
thanks a lot for the guidance

Was this reply helpful? Yes No
EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report

HI @Stefan68, this dates from a while but did you get this resolved. I see you're using SFDC? Can you elaborate more on your scenario and integration between SFDC and Power Apps/Dataverse? Thanks

Was this reply helpful? Yes No
stefan68 23 on at

Like (0)

Report

hi, no resolution on that unfotunately.

Was this reply helpful? Yes No