Skip to main content

Notifications

Announcements

No record found.

Finance | Project Operations, Human Resources, ...
Unanswered

Code Upgrade from AX 2012 R3 CU13 to D365FO On-premises using LCS -Issues / questions

(0) ShareShare
ReportReport
Posted on by 20

Hi everyone,

We have currently been operating on AX 2012 R3 CU13  and planning do trial / check of Code upgrade through LCS.

As a process, we have the Dynamics AX model store (Customization in VAR layer) and converted to Zip file as per Microsoft requisites.

Now when we try to create the project on LCS, we are able to see product name as "Finance and operations", however as per Microsoft document, it should be selected as "Microsoft Dynamics D365 Finance and operations On premises) . What could be the reason and how to get this resolved.

For the time being we have selected "Finance and operations", but then the project has only three step methodology (Learn --> Try --> Buy), however as per Microsoft document / online forum, it should have Five steps (Analysis --> Design and Develop --> Task --> Deploy --> Operate), What could be probable reason and how to get the same resolved.

For the time being we continue with case where LCS is providing three steps only. Now we have successfully uploaded the zip file (Ax Model store) on the portal.

In parallel, we have also generated personal security access token on DEVOPS (Visual studio) with Full access and linked the same with LCs under project settings --> Azure devops --> and selected the Axure Devops URL --> Token --> Axure dev ops project without any error or challenge.

Now when we have initiated the Analysis and done multiple times, however we have received error in all the cases:

a) Analysis has stopped after 76% (540 total item and 410 only done) and has given error "The work items could not be created for the Visual Studio Team Services project. Please verify the Visual Studio Team Services account has permissions to create and delete work items and then retry.". However when DEVOPs is checked almost 1013 work item were created. So in such case, error gives misleading information as it has stopped in between.

b) Analysis stopped after 80% (540 total item and 430 only done) and has given the error "We're sorry, the analysis can't be completed. To research this issue, see Find Support.", however we could not get the reason behind, why it has stopped. Also when we have checked the second project for this iteration, no wok item has been created on DEVOps Portal. Even when we have checked the REPOS, only AX 2012 folder was created, however other folder of D365 F&O has not been created with 10.0.8XXXX which should have been created during analysis and code update. What could be probable reason and how to get the same resolved.

c) Anaylsis stopped after 59% (160 total items and 95 progress) has given error "We're sorry, the analysis can't be completed. To research this issue, see Find Support." however we could not get the reason behind the same.Also when we have checked the second project for this iteration, no wok item has been created on DEVOps Portal. Even when we have checked the REPOS, only AX 2012 folder was created, however other folder of D365 F&O has not been created with 10.0.8XXXX which should have been created during analysis and code update. What could be probable reason and how to get the same resolved.

There seems to some challenge from Microsoft documentation and from Microsoft LCS side, where this Code Analysis / upgrade is not been done through LCS even after running the process multiple time.

Please suggest and let us know if there is some remedy / resolution.

Many Thanks,

  • Ashwani Jain Profile Picture
    Ashwani Jain 20 on at
    RE: Code Upgrade from AX 2012 R3 CU13 to D365FO On-premises using LCS -Issues / questions

    Hi JJ,

    After I have posted this concern on Dynamic Community, Microsoft has provided us with partner account (trial for 1.5 year) and the earlier part (Project creation) has been resolved with that 

    However when it comes to LCS challenges, we have been receiving the same error (The work items could not be created for the Visual Studio Team Services project. Please verify the Visual Studio Team Services account has permissions to create and delete work items and then retry) in our temporary partner account as well, where LCS is creating only 17 stories and 1000 work items all the time.

    We know that this integration between LCS and DEV Azure works on Personal Token and hence I have set the validity as 90 Days, hence this error could not be due to Token expiry.

    We have executed this process 5 times and got same count of work items (17 stories and 1000 tasks). After creating 1000 tasks, system gives the same error.

    This means there is some challenges / setup in LCS or DEV AZURE, where after creating 1000 + 17 (1017) work items, it does move ahead.

    Add Info: With same model store (AX 2012 customization), system has created different tasks in one of the iteration and not created for many other objects that has been created in other. This shows that all task / work items are not created and there is some 1000 limitations defined which has to be corrected to create all task (to complete code upgrade activity).

  • JJ_Yadav Profile Picture
    JJ_Yadav on at
    RE: Code Upgrade from AX 2012 R3 CU13 to D365FO On-premises using LCS -Issues / questions

    Hello Aswini,

    The methodology that have five steps is basically a customer implementation project methodology (Analysis --> Design and Develop --> Task --> Deploy --> Operate). This type of LCS project is created automatically for customer that have signed up for the Finance and Operations. This methodology is available only for customers who have purchase the minimum licenses. Customer and partners can use Migrate, create solutions, and learn the project for Finance and Operations apps to get started with upgrading the solution and lean. For more details please follow the link bellow.

    Lifecycle Services (LCS) for Finance and Operations apps partners - Finance & Operations | Dynamics 365 | Microsoft Docs

    To exercise LCS code upgrade service, you can utilize the LCS project Learn type LCS project and start working on the code upgrade . The error you are getting during the code upgrade could be seems to the permission related.  Code upgrade service uses the access token that is defined in the LCS project settings. Check that this token is created by user who is ADO project admin - and that the token is not expired. For detail check the community discussion.

    (+) The work items could not be created for the Visual Studio Team Services project. Please verify the Visual Studio Team Services account has permissions to create and delete work items and then retry - Dynamics 365 Finance Forum Community Forum

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

Congratulations 2024 Spotlight Honorees!

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December!

Congratulations to our December super stars! 🥳

Get Started Blogging in the Community

Hosted or syndicated blogging is available! ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,622 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,354 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans