Personalized Community is here!
Quickly customize your community to find the content you seek.
Now Available in Community - New TechTalk Videos for 2021
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
Thanks in advance.! Can you guys helps me with below question.
Q1. Why do we have two versioning for CPOS and MPOS. When we apply the version number and publisher name in customizationSetting file then build and deploy the package, the same is displayed in MPOS but it does not change in CPOS.
Q2. Do we have any way we can manage the same versioning for CPOS and MPOS.
Hi Pratyu, if you will not get any feedback from community members, please create Microsoft support ticket for us.
Ideally CPOS wont have any issue as it will be driven by scale unit (hope the correct package applied on scale unit). If you see the difference in version of MPOS and CPOS, it should be your MPOS which might not build correctly.
Check the version in MPOS installer -> right click and properties. If you are building your Retail SDK locally (not though pipeline) you should consider cleaning up all the bin and obj directories in Retail SDK. Sometime it wont get replaced/build properly and pick up older installer for MPOS.
Hope this helps you.
Business Applications communities