Invalid GUID when redirecting form On Success ( Virtual Tables )

(1) Share

Report

Posted on by SB-13031509-0

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

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Jon Unzueta 1,215 Super User 2025 Season 2 on at

Like (0)

Report
Invalid GUID when redirecting form On Success ( Virtual Tables )

@SB-13031509-0

This is a known issue when using Power Pages forms in Insert mode with Business Central virtual tables (v2.0). The GUID returned in the “Append Record ID to Query String” setting often does not match the actual Business Central record ID, especially immediately after creation. Here's what’s going on and how to work around it:

Root Cause

Virtual tables in Dataverse are essentially read-through proxies to Business Central.

When you submit a form in Insert mode, Power Pages generates a temporary GUID for the record.

However, Business Central creates its own record ID, and there is a delay (or mismatch) before the virtual table reflects the actual BC record.

This causes the second form (which expects the real BC record ID) to fail to load.

Workaround Options

1. Use a Custom Redirect Instead of “Append Record ID”

Instead of relying on the auto-appended GUID, use a custom redirect in the “On Success” settings:

Set “Redirect to URL” and pass a custom query string (e.g., a unique field like Sales Order Number or external ID).

Then, on the second form, use FetchXML or a Web Template to retrieve the correct record based on that field.

2. Introduce a Delay or Polling Mechanism

If you must use the GUID:

Add a server-side delay (e.g., via Power Automate or a plugin) to wait for the virtual table to sync.

Or, use a JavaScript polling loop to check when the record becomes available before redirecting.

3. Use a Custom Table as a Staging Layer

Create a Dataverse custom table to temporarily store the form data.

Use Power Automate to create the record in Business Central, then retrieve the actual BC record ID.

Redirect the user once the real record is available.

Additional Tips

This issue is more common when using anonymous access or non-verified users.

You can monitor the sync delay by checking the Dataverse virtual table logs or Business Central telemetry.

🏷️ 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.

Was this reply helpful? Yes No