Vibe Power Apps Unable to Remove or Add Table

(0) Share

Report

Posted on by PN-29062351-0

Hi all,

I’m currently building an app using the new Vibe (Try new experience – Preview). The app has been published several times for testing, and everything was working fine initially.

However, over the past two days, I’ve noticed that whenever I add a new Dataverse table to the app, the app immediately shows "Server disconnected. Trying to reconnect...". The newly added table appears for a few seconds, then disappears after about 5 seconds.

At the same time, I receive the following warning:

Changes not saved
We couldn't save your latest data model changes. We'll keep trying automatically. Last saved: unknown.

I've tried retrying multiple times, but the same issue occurs every time. Existing tables continue to work without any problems—this only happens when adding a new table.

Has anyone encountered this issue before or knows what might be causing it?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (8)

Answers (0)

Sort by

Suggested answer

11manish 3,323 on at

Like
a
(0)

Report
Copy link

Link copied!
This does not appear to be a problem with your Dataverse tables themselves. The symptoms strongly suggest a preview-related issue in the Vibe authoring experience or a temporary backend synchronization problem. If the issue persists after trying a different browser and verifying it also occurs in a new app, I recommend opening a Microsoft Support ticket. Include:

The environment ID

App ID

Approximate UTC time when the issue occurs

Browser console/network logs (if available)

Confirmation that the issue only affects newly added tables and that existing tables continue to function normally

This information will help Microsoft determine whether you're encountering a known issue with the Vibe preview experience.

Was this reply helpful? Yes No
PN-29062351-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks for the recommendation.

I tried to add the table using below prompt :

"Which existing table do you want to add to the app?

Employee name table — Add the existing Dataverse table that contains crbc0_EmployeeName.

How should the app use this existing table?

Lookup/picker — Use it to select employees or related records in the overtime form."

Getting this respond:

Implementation is blocked because the existing Dataverse table schema is read-only from this project, so I can’t add/configure the crbc0_EmployeeName table metadata here.

Add the existing table connection/metadata in Dataverse or the app data source configuration first, then I can regenerate the data layer and wire it into the overtime form picker.

Is there some configuration that i can edit to enable ?

Was this reply helpful? Yes No
SL-19111310-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!

To @PowerApps Dev Team, I have reported this issue today 06/30/26, I am having the same issue and seeing Vibe reverting the table after adding an existing Dataverse table. I add the table under Data, it looks like it worked, then it disappears or the app gets stuck on “Changes not saved”. Sometimes it turns into a Draft/InMemory table instead of a real Dataverse binding.
Error/symptom

- “Changes not saved. We couldn't save your latest data model changes. We'll keep trying automatically. Last saved: unknown.”
- Sometimes the table ends up as Draft/InMemory instead of a real Dataverse binding.

Was this reply helpful? Yes No
KA-30062315-0 4 on at

Like
a
(2)

Report
Copy link

Link copied!

I'm experiencing the exact same issue in our environment over the past few days, so you're not alone on this one.

Was this reply helpful? Yes No
KA-30062315-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!

Did anyone get any update?

I have already logged a ticket and nothing yet from PG team.

Was this reply helpful? Yes No
SL-19111310-0 4 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @KA-30062315-0, I’m in the same situation and am currently waiting for an update on this issue.

Was this reply helpful? Yes No
DD-02071425-0 2 on at

Like
a
(0)

Report
Copy link

Link copied!

I'm currently facing the same issue. I had an app which was working fine in my personal developer environment and published several times. Since last week however, I tried several times and it kept failing showing the same error message: Publishing data tables - Failed to create tables. Please try again.I have tested it in other environments and the error persists. For a day, the environment which I was previously using was even disabled in Vibe, showing a message that it was not eligible for the experience (even though it was). The environment eventually became enabled again but still no able to publish anything out of draft mode.
I have already a ticket opened for support and am currently waiting for an update.

Fai oi jkkkled to create tables. Please try again.

Was this reply helpful? Yes No
DT-30060822-0 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello;

I've been experiencing the same problem for about a week now. I've tried everything, but I can't add new tables to the system. As you mentioned, it immediately deletes the table and gives the same error message. It doesn't even allow me to add columns to existing tables, update the schema, update the plan, or update the SDK. I think Vibe itself is in some kind of deadlock mode. I can't introduce anything to the system other than the existing dataverse tables, and I can't add fields to the tables. The co-pilot agent in the command prompt tries to solve the problem but fails; that annoying error keeps occurring, the connection drops, and it deletes the added table. The UI thinks it's connecting the added fields to the dataverse table, but it can't because it can't change anything anymore.
We urgently need a solution to this problem.

Was this reply helpful? Yes No