Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We are facing above error from the enterprise portal when we click on the link which is generated (Email) during workflow approval process.
Ex URL : -Server:Port/.../EPPurchReqTableInfo.aspx
We are able to successfully open the purchase requisition list page from both AX and through EP. and checked the filters on the URL as well everything looks fine.
We were able to successfully redeploy the web controls and page Definition of “PurchReqTableInfo”. Can anyone share your experience to trouble shoot this error ?
Thanks in Advance
As mentioned URL is generated from the Workflow. We took one of the purchase requisition which we had the error in URL. And we opened manually the same purchase requisition from EP. And compared both the URLs everything looks same except the WHPV id.
Can anyone explain what WHPV id and from where it is getting generated from AX. is there any set up or configuration associated with it ?
Thanks in advance
I would suggest you create a case with Microsoft in regard to this issue.
There are a number of hotfixes listed on LCS.
I would recommend to review them and check them against your specific system version.
Unfortunately, you did not mention what AX2012 version you apply and therefore need to check yourself whether and what fix might apply.
If you cannot find anything, I would recommend reaching out to the MS support team.
Thanks for the suggestions,
We have raised the ticket with Microsoft.
Business Applications communities