web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Unanswered

missing activate deactivate buttons on workflow/process

(0) ShareShare
ReportReport
Posted on by 441

I have a workflow (process) where I am the owner.  I am an administrator of Dynamics/Powerapps.  

I could not see this workflow in the classic solution editor using Add Existing.

I can see it in the new solution editor.  So I added it to the solution for the current sprint.

The workflow moves portal created tickets (incidents) to a specific queue.  It works.

When I edit the workflow using the classic editor now, The only buttons on the command bar are  Close and Actions/email a link.

see image below

Does anyone know why this might happen?

pastedimage1678372545128v1.png

all of my other workflows appear thusly:

workflow-having-command-line-buttons.PNG

I have the same question (0)
  • Ray Profile Picture
    1,537 on at

    Not sure about the reason, but I think there are some things you can check about:

    1. Go to solution page and click Processes, select this workflow and see if the Activate/Deactivate button shows:

    pastedimage1678434918823v2.png

    2. Updating workflow status by Odata API and then check the workflow page to see if the button shows.

    var entity = {};
    entity.statecode = 1; // 1 = Active, 0 = Inactive
    var id = "E03A6A96-857D-4DB2-AF20-BF950D74548D"; // replace it with your workflow id, you can get it from the URL when you open the workflow in the browser
    var req = new XMLHttpRequest();
    req.open("PATCH", Xrm.Page.context.getClientUrl() + "/api/data/v9.1/workflows(" + id + ")", true);
    req.setRequestHeader("OData-MaxVersion", "4.0");
    req.setRequestHeader("OData-Version", "4.0");
    req.setRequestHeader("Accept", "application/json");
    req.setRequestHeader("Content-Type", "application/json; charset=utf-8");
    req.onreadystatechange = function () {
    if (this.readyState === 4) {
    req.onreadystatechange = null;
    if (this.status === 204) {
    //Success - No Return Data - Do Something
    } else {
    Xrm.Utility.alertDialog(this.statusText);
    }
    }
    };
    req.send(JSON.stringify(entity));

    3. Check the console log in browser developer tools, and check about the html for these buttons.

  • urklnme Profile Picture
    441 on at

    and the answer is......

    I exported the solution to which I added the process.

    in that solution I found the workflow definition for that process.

    I noticed that it had a property named RendererObjectTypeCode with a value of 8181.

    I looked up the entity type code of 8181 SHAZAM!!  Routing Rule

    sysadmin-central.com/.../

    Setting/Service Management/Routing Rule Sets/<process name>

    pastedimage1678460041174v1.png

    the routing rule actually creates a workflow.  this workflow does not appear in the classic solution editor, in the processes tab.

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.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
ManoVerse Profile Picture

ManoVerse 180 Super User 2026 Season 1

#2
11manish Profile Picture

11manish 123

#3
CU11031447-0 Profile Picture

CU11031447-0 100

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans