Power Platform Community Forum Thread Details

Invalid GUID when redirecting form On Success ( Virtual Tables )

Hello There!
I have an issue with a Power Pages form (Insert mode) using virtual tables (v2.0) from Business Central. In "On Success" settings, I use "Append Record ID To Query String" to pass the GUID to a second form. However, the GUID is random and doesn’t match the new Sales Order record, causing the second form to fail to load. I suspect a sync delay with virtual tables. Has anyone had this problem?

Categories:

General topics

@Bukhtiiarov

hanks for sharing your issue—this is a known challenge when using Power Pages with virtual tables (v2.0) from Business Central, especially in Insert mode where you're trying to pass the newly created record's GUID to another form.

✅ Issue Summary

You're using “Append Record ID to Query String” in the On Success settings of a Power Pages form.
The form is connected to a virtual table from Business Central.
After submission, the GUID passed is random or incorrect, and doesn't match the actual Sales Order record.
This causes the second form (which expects a valid record ID) to fail.

❌ Why This Happens

This behavior is likely due to a sync delay or mismatch between:

The Dataverse virtual table record created via the form.
The actual Business Central record that gets created asynchronously.

Virtual tables in Dataverse do not store data locally—they act as a proxy to external systems like Business Central. When you create a record via Power Pages:

The form may generate a placeholder GUID.
Business Central creates the actual record with its own ID.
The virtual table may not immediately reflect the correct ID, especially if there's a delay in syncing or mapping.

✅ Workarounds & Recommendations

1. Use a Custom Redirect with Business Central ID

Instead of relying on Append Record ID to Query String, consider:

Using a custom redirect in the On Success settings.
Retrieve the actual Business Central record ID (e.g., Sales Order No.) via a plugin or Power Automate.
Pass that ID in the query string to the second form.

2. Use Power Automate to Bridge the Gap

Create a Power Automate flow that:

Triggers on form submission.
Retrieves the correct Business Central record.
Updates a Dataverse table with the correct GUID or reference.
Redirects the user to the second form with the correct ID.

3. Delay the Redirect

If the sync delay is short, you can:

Add a short delay (e.g., 5–10 seconds) before redirecting.
Use JavaScript to poll the virtual table until the correct record appears.

4. Use a Lookup Instead of Direct ID

If possible, use a lookup field (e.g., Sales Order No.) in the second form to retrieve the record, rather than relying on the GUID.

🏷️ Tag me if you have any further questions or if the issue persists.

✅ Click "Accept as Solution" if my post helped resolve your issue—it helps others facing similar problems.

❤️ Give it a Like if you found the approach useful in any way.

Quick Links

Subscribe to this forum!

Stay up to date on forum activity by subscribing.

Leaderboard > Power Pages

Fubar 62 Super User 2025 Season 2

Community site session details