Unanswered

Liquid - entities object doesn't work

(0) Share

Report

Posted on by bilgybabu

Our system uses Power pages with enhanced data model enabled. We have several pages using liquid template code and has been working fine. After the Power Pages release - 9.5.6.x GA Wave 1 that occurred on 30th July, fetching records using entities liquid object stopped working.

Liquid template lines like entities.contact[guid] now throws an error: Liquid error: Sequence contains no elements

The same fetch on Contact entity records works well if the above line is replaced by liquid fetchxml query.

I opened a ticket with Microsoft, but they haven't responded yet. Is anyone else facing this issue, or have a solution to this?

Categories:

General topics

I have the same question (0)

All responses (24)

Answers (0)

Sort by

Lucas001 2,562 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @bilgybabu,

I am using the enhanced model as well, but got limitations.I am using a custom table with the same liquid as you do.

Could you test another table instead the contact table is a systems' table. Maybe they changed something on the table itself, what would probably effect all of us at some point.

Was this reply helpful? Yes No
bilgybabu 22 on at

Like (0)

Report
Copy link

Link copied!

Hi @Lucas001 ,

I do have other pages fetching custom entity records like this, it stopped working there as well.

For testing, I created a trial environment with 2 power pages site one on standard and the other on enhanced data model. The issue exists on the one with enhanced model but not on the other one. What region your site is on and could you check on the admin centre if you received a notification for the release occuring on July 30th (We received the notification on 27th July)?

Was this reply helpful? Yes No
Lucas001 2,562 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi @bilgybabu,

I just checked right now as I am using the way to give the customer the possibility to change textsamples themselves.
I am using the below liquid and use the variable with {{ textheader }} inside a html tag. And it works fine for me.
{% assign textHeader = entities.test['8f6138f1-test-test-9cbc-6045bd8be48b'] %}

As far as I can see it we got no notification. But I am not a global admin, so I cannot say for sure.
What does the message say?

If the support solves your solution please keep us updated as we might come across the same problem as you just did.

Was this reply helpful? Yes No
bilgybabu 22 on at

Like (0)

Report
Copy link

Link copied!

Hi @Lucas001 ,

This is what the release notification said:

Our DEV and UAT portals were marked for upgrade in this notification and I can confirm that it stopped working right after this release.

Like I said, for testing this, I also set up a trial environment with one standard model and one enhanced model site, and this way of fetching records doesn't work in the enhanced model site, while the other site works perfectly fine.

Thanks!

Was this reply helpful? Yes No
Lucas001 2,562 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi @bilgybabu,

strange behaviour. But as spoken with a lot of Community Members the enhanced data model is right now really in preview. And after working with it since the beginning, I currently cannot recommend it as there are to many bugs.

Did the support manage to answer or help you?

Was this reply helpful? Yes No
bilgybabu 22 on at

Like (0)

Report
Copy link

Link copied!

Nope, no reply yet.

Was this reply helpful? Yes No
Lucas001 2,562 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @bilgybabu,

there are some updates to the power pages core package and some others for power pages since yesterday.
Did you install them? Maybe those will solve your problem as I faced a similar issue at the weekend which is now solved.

When your page is broken after installing the update, the problem refers to https://learn.microsoft.com/en-us/power-pages/admin/upgrade-site#solution-update. Waiting some time, in my case approx. 2h solved the issue.

Was this reply helpful? Yes No
seangoodlip 4 on at

Like (0)

Report
Copy link

Link copied!

We are currently facing the same issue but I noticed that this only happens on custom tables. Did you manage to get any response from MS support please?

Was this reply helpful? Yes No
Lucas001 2,562 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Fortunately for me the new update solved the issue and I can now work fine again.
Did you install your updates to the latest version, restart the page and tried it again?

Other than that I have no news, unfortunately.

Was this reply helpful? Yes No
bilgybabu 22 on at

Like (0)

Report
Copy link

Link copied!

@Lucas001 For me the update has not fixed the issue and there is very little help from Microsoft on this yet. Now I'm noticing new issues with Enhanced data model. Basic form/Multistep from Metadata doesn't seem to function right. 'Set Value on save' metadata set on any Basic form appears to be effecting all basic forms. Like, let's say I have a basic form on Contact and a metadata for setting value on save for statuscode. This appears to be setting statuscode for all basic forms in the system, If I have an Account basic form, saving the record on that basic form seems to be trying to set statuscode. Have you noticed anything like this?

Was this reply helpful? Yes No