Resolve Power Apps Vibe Runtime Errors
Publicada el 2026-07-29
Descripción de la oferta
Power Apps Vibe/Code App Data-Source Manifest RepairI have a cloud-only app created through the new Power Apps Vibe experience. The app uses existing Dataverse tables and recently added Microsoft 365 MCP connections for Calendar, Mail, and Work IQ. After adding the M365 connection, the app’s generated runtime data-source manifest appears to have been overwritten or regenerated incorrectly. Current condition: power.config.json still lists all required Dataverse tables. .power/dataverse/* still contains the Dataverse schemas. src/generated/* still contains the generated models, hooks, and services. The actual Dataverse tables and records still exist. .power/appschemas/dataSourcesInfo.ts now contains only a365mcpservers. It no longer registers Company, State, Contact, Activity, or the other Dataverse sources. Generated services still expect data-source names such as Company and State. This causes runtime errors such as: Retrieve multiple records operation failed: Data source not found: craa5_company4s and: Data source not found: new_states Confirmed core mappings include: Company: craa5_company4 / craa5_company4s Contact: new_contact Activity: new_activity State: new_state / new_states Additional affected tables include Insurance Metrics, Employment, Company Metrics, mutual-company tables, and AM Best Rating History. The app is cloud-only in Power Apps Vibe. The Vibe Copilot cannot edit protected generated files or run PAC CLI, and external PAC deployment may create a separate app disconnected from the original Vibe plan. Assistance needed I need someone experienced with Power Apps Vibe/code apps, Dataverse data-source generation, and PAC CLI to: Diagnose why adding a365mcpservers removed the Dataverse runtime registrations. Restore/regenerate every existing Dataverse data-source registration. Preserve the current app, plan, Dataverse tables, records, relationships, UI, and recent code changes. Preserve or safely reconnect the M365 Work IQ, Calendar, and Mail sources. Ensure the Dataverse and M365 sources coexist in the runtime manifest. Avoid manually fabricating generated metadata unless Microsoft specifically supports that repair. Test Companies, Contacts, Activities, State map/detail drawer, Insurance Metrics, Employment, Calendar, and Mail in the actual published runtime. Establish a safe backup/recovery point before making changes. The freelancer must not: Create replacement Dataverse tables. Delete or migrate existing records. Rebuild the app from scratch without approval. Replace generated services with mock data or raw Web API workarounds. Claim success based only on TypeScript/build validation. Expected result: dataSourcesInfo.ts includes the required Dataverse registrations plus a365mcpservers. CompanyService.getAll, StateService.getAll, and other generated services work in the published app. M365 Calendar and Mail remain connected without overwriting Dataverse. All current UI and navigation behavior remains intact. Asking specifically for someone familiar with the 2026 Power Apps Vibe preview experience, not only traditional canvas or model-driven Power Apps. This looks like a generated-manifest/ALM problem rather than a React page bug.
Skills
Fuente original: freelancer