Business Process Flow broken after upgrading from CRM 2016 to 365 On-Prem

(2) Share

Report

Posted on by JVE

213

Lately updated test environment from CRM 2016 SP1 to 8.2.0.749 (Dynamics 365 On-Premises)

Built in (OOB) and custom business process flows don't work for either newly created or existing records. I cannot switch process flow. I cannot proceed to next stage. Either with GUI or javascript. When I press Next Stage, it kind of jumps to next stage, but the active one remains the previous one.

So, given 2 organizations: TEST (newly created Dynamics 365 Org) and EXIST (existing one, upgraded in-place, including database. This DB was created at least with version CRM 2013, could be even CRM 2011)

Trying to debug situation:

Create a new, empty organization (TEST) and import our custom solution: OOB and custom Business Process Flows do work. Ok, that means fresh Organizations have no problem.
Reimporting solution within existing organization (EXIST) that was upgraded - doesn't help.
Activating, deactivating, changing Business process flow ownership - doesn't help.
Importing EXIST backup from CRM2016SP1 as another organization - doesn't help.

I did capture HTTP requests from both organizations: TEST, EXIST. The requests match, no problem (only record id's different). Comparing response, I see that traversedpath and stageid remains old one for EXIST oganization. For TEST organization it returns new stage and traversedpath values correctly. So that means that there is no problem with CRM UI or HTTP request, but it has to be within application logic/database.

I did try to capture requests for BusinessProcessFlowInstance and ProcessStage tables/views to see if anything suspicious happening there like SQL errors or no data returned or something. For EXIST organization, 3 SQL SELECTs where issued and nothing more. For TEST, many more requests were issued, including UPDATE/INSERT statements. However, nothing suspicious for those 3 SQL SELECTs for EXIST organization: they all contained valid data compared to TEST.

One step in business process flow appears to work when entity transition happens, when qualifying LEAD -> Opportunity. But when on opportunity, no longer business process flow steps work.

Couldn't find anyone having such problems. Ideas?

*This post is locked for comments

I have the same question (0)

All responses (18)

Answers (1)

JVE 213 on at

Like (0)

Report
I don't know if it is possible to change process in code, but I did try doing this and it didn't help:

Entity updateOpportunity = new Entity("opportunity", opportunity.Id); updateOpportunity["stageid"] = new Guid("1b5cc994-b77b-7de7-adec-0670595dc475"); updateOpportunity["traversedpath"] = "0b777d40-3f5b-4687-8d90-cb4d650189cc,1b5cc994-b77b-7de7-adec-0670595dc475"; PrintEntityAttributes(updateOpportunity); service.Update(updateOpportunity);

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi I read your question. It has raised a question for me which I cannot get a straight answer on. At what point will Dynamics CRM On prem become obsolete? is the a relevant question?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Maybe stupid, but can you check that id of BPF (processid) in your records matches id of your BPF? Maybe for some reason they are different.

Was this reply helpful? Yes No
JVE 213 on at

Like (0)

Report

Yes, they do match. That's why I said that, looking at SQL tables, nothing suspicious there.
During HTTP Request/Response, I see that correct process id is being passed.

I won't be able to debug this any further, as I had to rollback our environment so we can get some work done. So I hope maybe someone has encountered this and has a solution for it so we can try another update attempt.

Was this reply helpful? Yes No
danbrunn on at

Like (0)

Report

I ran into a similar situation with my CRM 2016 BPF - after upgrading to Dynamics 365 On-Premise, only new records with the BPF worked. After some SQL debugging, i noticed that the pre-existing BPF's were missing UniqueName, and BusinessProccessType in the workflowbase table. Once i added these, my BPFs in Dynamics 365 started working again. I spoke with MS, and this is a known bug and is supported.

Was this reply helpful? Yes No
JVE 213 on at

Like (0)

Report

Thanks for the tip. I left CRM 365 DB hanging aound and I can see that for Custom BPF, UniqueName and BusinessProcessType IS populated. For most built-in bpf, they are empty.

However on CRM 2016 DB, UniqueBame is empty for all BPFs, but BusinessProcessType populated exactly like in CRM 365.

Moreover, even for new records BPFs don't work.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Dealt with MS on this earlier this week after our update last weekend. It is a known issue after update to newest version. I was assured they are working on it. No new updates since Tuesday.

Was this reply helpful? Yes No
JVE 213 on at

Like (0)

Report

Thanks. Would be nice if you could post here any updates on the issue. But that looks like next CRM Update is mandatory :)

Was this reply helpful? Yes No
danbrunn on at

Like (0)

Report

I'm curious since you said your UniqueName & BusinessProcessType columns were filled in - did you attempt at 'save as' of your business process flow and set the newly copied as the primary flow? Before navigating to the db to manually update those columns, this worked for me in initially fixing the failing BPFs. I assume this would have failed as your issue is definitely different than mine.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hello

Based on your business process I would say yes, a CRM does sound like a good option in running your business more efficient. A CRM allows you to keep a record of your customers' details and any interaction so it makes everything well organized.

You may also want to look at the option of getting a CTI solution like Tenfold which integrates your existing phone and CRM. Checkout these integrations at www.tenfold.com/.../dynamics

Was this reply helpful? Yes No