How can I configure an Advanced Form Step to point to a record referenced by the record in the previous step?

[Michael_Cullen]

I have created an Advanced form where the first step points at the Account table, and the second at an Account_Expansion table.

In the definition of the first step, it is set to point to the "Record Associated to Current Portal User"

I want the second step to display a form for the Account_Expansion table. The Account table contains a Lookup to the Account_Expansion table (and the Account_Expansion table contains a Lookup to the Account table). I would like the user to view/edit the Account record, and then move on to view/edit the related Account_Expansion record. Is there a way I can do this?

I thought this would be possible using a query string as a Record source for the second step, but when I do this using the only selectable options, as in the below screen-shot, an unrelated empty record is displayed on the second step...

[Fubar]

Usually the query string option is used on the First step, I believe there is no out of the box way to do this however.....

• Avoid using the default "id" for the Query Source identifier on the 'edit parent step' (as 'id' is already being used) e.g. use something else of your choosing in the example below I use "xyzid"
• On the previous Step add some custom JavaScript to get and then inject the guid of the record you want to edit into the "<form" tag for the Step - so you get something like the following on the previous step

<form method="post" action="/test2/?id=077174ee-fbc4-ec11-a7b5-000d3a6b58c1&xyzid=5868ecdf-fbc4-ec11-a7b5-000d3a6b58c1" onsubmit="javascript&colon;return WebForm_OnSubmit();" id="content_form">

[Michael_Cullen]

Thanks, @Fubar, I've been following your suggestion, and trying along those lines. One issue I've run into is that I'm finding that I cannot retrieve all the fields of the Account table using liquid. For example,

{{user.contact_customer_accounts.accountid}}

and

{{user.contact_customer_accounts.address1_city}}

return values,

but

{{user.contact_customer_accounts.accountNumber}}

{{entities.account['07e08cad-9494-ec11-b400-0022489e3524'].accountNumber}}

 or

{{entities.account['07e08cad-9494-ec11-b400-0022489e3524'].cr8b4_accountexpansion.cr8b4_account_expansionid}}

 do not.

Do you know whether there is anything which determines which fields are accessible using liquid? From my reading of the documentation, I believed the entities keyword would allow one to obtain any specified field of a given record...

[Fubar]

Not sure what you are trying to do now.

Reading between the lines

"." notation does not work for all object types and sometimes you need to use ['field_name'] notation.  And just because you have access to a record does not automatically give you access to values its related records (e.g. a Lookup on the record will generally just give you its internal GUID that you then use to make another call to retrieve the record linked to the lookup - or you use fetchXML to condense into one query)

But also 

a) accountNumber is probably accountnumber (case matters)

b) entities.account['07e08cad-9494-ec11-b400-0022489e3524'].cr8b4_accountexpansion.cr8b4_account_expansionid is probably entities.account['07e08cad-9494-ec11-b400-0022489e3524'].cr8b4_account_expansionid  (or more likely entities.account['07e08cad-9494-ec11-b400-0022489e3524']['cr8b4_account_expansionid'] )

see https://docs.microsoft.com/en-us/power-apps/maker/portals/liquid/liquid-objects#entities

[Michael_Cullen]

My apologies - my reply was not very clear. However, your reading between the lines was correct - I have been trying to obtain the internal GUID of the related record in the account_expansion table from the relevant lookup in the account table. My intention was then to make another call to obtain the related record itself, as you suggest.

Thanks for clarifying the distinction between the dot (".") notation and the field name (['']) notation - I was not aware that the dot notation did not always work.

I've corrected my syntax and experimented with accessing different fields on the Account entity, and it seems like I can retrieve the content of most fields, except Choice and Lookup fields, which consistently evaluate to empty strings.

[Fubar]

---

I've corrected my syntax and experimented with accessing different fields on the Account entity, and it seems like I can retrieve the content of most fields, except Choice and Lookup fields, which consistently evaluate to empty strings.

---

This is probably because they are multidimensional (but depending on what you are doing could also be the caching e.g. a rece4nt update in DataVerse not pushing values through as its not synched yet)

• Lookups: .id and .name e.g. in dot notation result.fname.id or result.fname.name
• Picklists: .label and .value