Announcements
We've got a couple of Dev-Test/self-service/OneBox environments (call them A & B), both running 10.0.18 PU42 (7.0.5968.16999). A DB backup from A was recently restored on B to apply a desired/known config state, but one of the workflows now refuses to be edited in environment B: the ClickOnce Application launcher is shown, but then an "Unexpected error" dialog with the message Id not set Parameter name: elementId. The same workflow is still editable in environment A, and other workflows are editable in B (to the extent that our pragmatic solution is to simply create a new workflow and set it as default for the relevant module), but I've been surprised not to find anyone discussing this error elsewhere on the forums. Are there workflow-related tasks that I should have included alongside the DB restore? I've looked at Event Viewer on box B and not seen anything clearly relevant, but perhaps there are other avenues for investigation people would recommend?
Hi Rich,
Are the deployed models on both environment the same? Or are there any differences in customizations? Does it give an error for all workflow types or just one specific? Is it related to a custom workflow or one out of the box? Which workflow type gives the error?
Have you already tried to perform a full build of the models and a database sync job?
Did you identify the root cause for this and resolve this issue (without replacing the existing workflow)?
We've just done the upgrade to 10.0.20 (including some custom code) and are experiencing the same issue on selected workflows only.
Thanks,
André: Sorry for slow reply. I keep forgetting that the Email me replies to this post setting doesn't appear to work... I haven't tried a full build & sync in the problematic environment because, whilst it is a OneBox environment, we don't generally use it like a Dev environment, but rather use it to test our deployment process. The deployed models & customisations are the same, and it is just one specific workflow (of type TrvDocumentTemplate) that has the issue, with others opening in the workflow editor as you'd expect.
Christine: I'm afraid it was a workaround rather than a solution for us: we replaced the workflow, and I've just deleted the one that wouldn't open. This wasn't possible at the time, so I suspect that in-process workflow instances were preventing deletion. I'm slightly surprised they were able to progress through to completion, but that's my best theory. I can only hope you're able to recreate your workflows without too much effort.
Thanks for the quick reply. We do have backups of our workflows, so that's not an issue, but I was hoping to find another way around it and also get to the bottom of why this occurred. I'm still looking into a few things and have also raised a Microsoft ticket in the mean time, so we'll see what happens.
I'll post an update on here if we can get to the bottom of it!
Regards,
Christine
Hi Christine,
We are also facing same issue for a particular workflow, Could you confirm if your issue is resolved and also please let me know if Microsoft has provided any solution or hotfix for the same.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Jump in, show your community spirit, and win prizes!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Giorgio Bonacorsi 676
Abhilash Warrier 633 Super User 2026 Season 1
André Arnaud de Cal... 624 Super User 2026 Season 1
