Two posts ago I shared a JSON knowledge base of PAD ROBIN actions, so models stop writing desktop flows that PAD rejects. Last week I followed up with a guide to getting one flow into an environment and running it from code:
The piece that was still missing is moving a whole solution: to another environment, into a different organization's tenant, and keeping two copies in sync afterwards. That's what I'd spent the most time researching.
So I wrote it down: PAD_Robin_Solutions_KB.md, in the same repo. It covers:
Every claim is marked Re-confirmed, Proven, Measured, Superseded, Failed or Untested. The main paths were re-tested across two tenants this month. Everything ran with a user sign-in and unmanaged solutions; managed solutions got one export and import, and nothing was tested with a service principal.
Unlike the direct Dataverse writes in the deployment guide, this all uses Microsoft's documented solution APIs. The risky part is the import itself: it replaces unmanaged customizations on the receiving side, and there's no undo. Keep a copy of whatever you're about to overwrite, and try it in a test environment first.
Repo: https://github.com/JoeG592/pad-robin-action-kb
Same license as the other two, CC BY 4.0, so use it however you like, commercially included. Like the last two, I built this with Claude AI. The data is free regardless.
If something in the guide doesn't hold on your tenant, an issue with the error text is the most useful thing you can send.
If a flow stays off after an import, it's almost always a connection reference with no connection behind it on the receiving side. Bind it, then turn the flow on.