Update the RapidClaw Dataverse Solution
For administrators of RapidClaw for RapidStart Apps in a Microsoft Dataverse environment.
Solution updates are separate from runtime updates
The Dataverse solution supplies the RapidClaw host components and launcher. Updating it does not, by itself, upgrade an installed OpenClaw runtime. Hosted Setup and runtime releases have their own lifecycle; not every RapidClaw release requires a solution update.
Before you begin
- Confirm the Microsoft tenant, environment name, and Dataverse organization URL. Record the installed RapidClaw solution version.
- Use an administrator authorized to update solutions in that environment. These are permissions for the human administrator, not a reason to grant the connector application user System Administrator.
- Review the release instructions, confirm a recent environment backup is available, and test in a sandbox before updating production where practical.
Update a Marketplace-installed app
- Open the Power Platform admin center. Choose Manage > Environments and select the intended environment.
- Open Resources > Dynamics 365 apps. Find the package that installed RapidClaw and check its publisher and update status. The portal category name does not mean Dynamics 365 is required.
- If an update is offered, select the app and choose Update. Review the details and terms, then confirm.
- Wait for completion and refresh the status. Resolve reported installation errors before continuing.
Microsoft documents this process under managing apps in Power Platform. If the package is not listed or no update is offered, confirm the delivery method with your partner; do not uninstall the solution to force an update.
Verify the update
- Confirm the expected version in Solutions, then refresh your RapidStart app and reopen RapidClaw from the RapidStart Settings app
- Verify that Setup opens for the correct organization and your existing deployment is recognized. If it instead offers an unexpected new deployment, stop and check the environment before proceeding.
- Open Command Center and check connection readiness, existing Agent Packs, and access. Review any release-specific follow-up tasks before resuming affected work.
Do not reset or remove the deployment to update
Uninstall, Reset, and teardown are not routine update steps. Do not delete solutions, business records, application users, or Azure resources to resolve an update error. Give your partner the environment, installed and target versions, and error or import log, with secrets removed.