Finance | Project Operations, Human Resources, ...

The workflow is not appearing in the Dev environment.

(3) Share

Report

Posted on by charanch

242

Hi All,

We customized the Return Order workflow for both the Dev and UAT environments. Recently, we noticed that the workflow is not visible for newly created Return Orders in the Dev environment, while it is working as expected in UAT.

I checked the workflow configuration in Sales and Marketing > Workflows and found that the active workflow versions are different:

Dev Return Order Workflow Version: 1.19.0.0
UAT Return Order Workflow Version: 1.22.1.0

I have a couple of questions:

Could the workflow version difference be the reason why the workflow is not appearing on newly created Return Orders in Dev? I also noticed that some older Return Orders in Dev still display the Workflow button, and a few of them have already been submitted and completed successfully.
In UAT, the Workflow button is displayed by default when a Return Order is opened. However, in Dev, the Workflow button is not displayed at all for newly created Return Orders.

Could you suggest the best troubleshooting approach? Specifically:

Is there anything that can be verified or fixed through the application (workflow configuration, activation, workflow assignment, etc.)?
Or does this issue likely require investigation in the code (customizations, form extensions, workflow provider, security, or deployment)?

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (12)

Answers (0)

Sort by

Subra 2,133 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hi

Do you have the same issue for all the users and only for the specific users and did you added any customization to enable / Disable the workflow in return order.

Additionally, Version doesn't affect the workflow visibility in D365FO and check the below navigation as well for the workflow activations.

Accounts receivable > Setup > Accounts receivable workflows.

Thanks,
Subra

Was this reply helpful? Yes No
Suggested answer

Anton Venter 21,175 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

@charanch

I suggest to use the debugger to find out what's going. The workflow is usually driven by a status field and there could be some extra logic added or some other reason that's causing this behaviour.

Was this reply helpful? Yes No
charanch 242 on at

Like (0)

Report
Copy link

Link copied!

Hi @Anton Venter ,

Could you please suggest me where should i keep breakpoint any class or methods would be helpful.

Was this reply helpful? Yes No
Subra 2,133 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hi

Since the workflow has been enabled for the old records and it's not visible for the new records. please enable the debugging active method and additionally you can canSubmitToWorkflow method as well.

Thanks,
Subra

Was this reply helpful? Yes No
Anton Venter 21,175 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

You wrote that you have a custom workflow so I can't tell you exactly where to put the breakpoint. I can however give you a hint. If you look at the PurchTable form, the form has a canSubmitToWorkflow method. Your form should have that as well somewhere but in an extension class of course.

I see the standard Return form does not have a workflow so I am using the PurchTable form as an example.

Was this reply helpful? Yes No
charanch 242 on at

Like (1)

Report
Copy link

Link copied!

Hi @Anton Venter and @Subra,

I found this piece o code in return order form extension and salestable extension, I put debugged for this method and i changed my cursor from record to record still it is not triggered, even this method is not used in any method , i checked through find references. I'm working first time on workflow so any insights to go forward.

[ExtensionOf(formstr(ReturnTable))]
final class AZReturnTableForm_Extension
{
public boolean canSubmitToWorkflow()
{
boolean workflow;
FormDataSource formDataSource = this.dataSource(formDataSourceStr(ReturnTable, SalesTable));
SalesTable salesTable = formDataSource.cursor();

next canSubmitToWorkflow();

workflow = salestable.canSubmit_Return();

return workflow;
}
}

[ExtensionOf(Tablestr(SalesTable))]
final class AZSalesTable_Extension
{
public boolean canSubmit_Return()
{
SalesLine salesLine;
boolean ret = true;

ret = ret && (this.T_ReturnWorkFlowStatus == T_SalesOrderApprovalStatus::NotSubmitted);

select firstonly RecId from salesLine
where salesLine.SalesId == this.SalesId
&& salesLine.T_ReturnWorkFlowApproval == T_WorkFlowApproval::Approved;

ret = ret || (salesLine.RecId != 0);

return ret;
}

Was this reply helpful? Yes No
Subra 2,133 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hi

Could you please check whether you workflow has been enabled on the below Path.

Accounts receivable > Setup > Accounts receivable workflows.

Was this reply helpful? Yes No
Anton Venter 21,175 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

@charanch

In addition to Subras suggestion, there are actually many things to check but me do one more guess. Has the form been extended and the workflow properties been set properly on the form extension? See image below.

Finally, because there are many things to check on a custom workflow. I suggest to find a good article about creating new workflow types and then compare your custom workflow with that.

Workflow properties on form

Was this reply helpful? Yes No
Subra 2,133 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hi

Please verify all your configuration from the scratch, so that you can easily identify the issue.

Edit:

Additionally, you can refer the below blogs for more information.

https://community.dynamics.com/blogs/post/?postid=e1fcfdc8-1bfb-ee11-a1fe-6045bdec599f

https://dextersdax.blogspot.com/2020/09/create-custom-workflow-d365-finance.html

Thanks,
Subra

Was this reply helpful? Yes No
Anton Venter 21,175 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

@Subra

My suggestion about checking the entire workflow was clear, no?

Was this reply helpful? Yes No