Recently I struggled to navigate between custom pages in Power Fx while passing a record as context. The error was vague and the solution wasn’t obvious.

The Problem

I tried the straightforward approach:

Navigate('App Name', record);

This threw a generic error: “Unsupported property ‘_ownerid_value’.” The error message didn’t point to the real issue, making it difficult to diagnose.

The Solution

The trick is to wrap the record in an object:

Navigate('App Name', { Record: record });

That’s it. By wrapping the record in an object with a named property, Power Fx can properly pass the context to the target page.

Why This Works

When you pass a bare record, Power Fx tries to destructure its properties directly, including internal properties like _ownerid_value that aren’t meant to be exposed. By wrapping it in an object, you’re telling Power Fx to treat it as a single, named context variable that the target page can reference.

Takeaway

Small syntax changes like this can be annoyingly hard to spot. If you’re getting cryptic property errors when navigating with records, try wrapping your context in an object first.

For more details on the Navigate function and its parameters, see the official Power Fx Navigate documentation.