Category: Microsoft Dynamics 365

401 Not Authorized error while access project in VSTS


Recently one of our users was getting the below error while trying to access the VSTS Project.

401 NOT AUTHORIZED and the following account does not have sufficient permissions to complete the operation. The following permissions are needed to perform this operation. View project level information.

Here we can see the users being added to the project team and the team having all the appropriate rights.

Adding the user to other groups i.e. Build Administrators, Contributors, Project Administrators etc. also didn’t help.

Also, inside Manager Users section.

https://[[subscription]].visualstudio.com/_admin/_users

We selected the user and clicked on Manage Projects to check his access.

It showed the user being part of Project Administrators – VSTS Groups.

Still user was getting the same 401 Unauthorized error.

https://developercommunity.visualstudio.com/content/problem/342094/401-unauthorized-error-for-a-user-added-to-project.html

https://developercommunity.visualstudio.com/content/problem/76468/cant-connect-to-tfs-401-not-authorized.html

Not sure what happens in the background and it takes time for the change to propagate. We have faced this issue many times with certain set of our users (one thing we have noticed that these users had their Gmail or Yahoo id associated to VSTS). For some users it has always worked properly (one using Outlook, Hotmail and Corporate account)

Hope it helps..

LookupRecordNotAvailable error while using Configuration Migration Tool in Dynamics 365 Customer Engagement


While trying to migrate the record using the Configuration Migration Tool, we were getting error like below in the log

ImportEntity – Result: True – Entity: transactioncurrency – Adding transactioncurrency to the reprocess List as field createdonbehalfby with value 05d52058-eb35-41e8-8af7-dfb7120c4599 – LookupEntity systemuser and Record Id 2655712b-e13b-e711-80fb-5065f38b5691 (SYSTEM) – (action:Update) failed validation for reason code: LookupRecordNotAvailable

As we do not want to migrate the createdonbehalfby field, the easiest fix for this is to remove the field from the schema.

Ideally instead of adding the entire Entity, we should select only those fields whose value we want to migrate in the Schema file.

Hope it helps..

Dynamics 365 and Office 365 in different tenants – How to consolidate !!


very insightful !!

Beth B - MCT, MCSE , MCSA, MSCP's avatarBethB-D365.com

tenantWe have run into many scenarios where a company has Office 365 and then orders Dynamic 365 from a CSP (Cloud Service Provider) and their systems end up different tenants.  As Microsoft moves to the model where there can be more than one partner of record and various flavors of Dynamics 365 (Finance and Operations, Business Central, Customer Engagement, etc..),  I can see this problem getting more prevalent over time.

When your Office 365 and Dynamics 365 are in different tenants it becomes quite the challenge and inconvenience.   A few major issues are as follows

  1. Server-Side Sync – only supports single tenant.
  2. Single sign-on – need to log into two systems.
  3. Two systems to manage
    1. Users
    2. Licensing
    3. Notifications
    4. Double the security concerns
    5. Double the competencies efforts
    6. etc… 

You say, heck this is easy, let’s just move our Dynamics 365 to the other tenant.  If it were on Premise it would…

View original post 2,241 more words

Dynamics 365 Saturday – Dynamics 365 Top 20 Tips & Tricks


Awesome tips and tricks. A must read 🙂

Microsoft adds two more Dynamics 365 AI apps to its roadmap


Techie.Buzz's avatarTechie.Buzz

Microsoft is adding more AI-infused Dynamics 365 applications to its line-up. In addition toe the previously announced Dynamics 365 AI for Sales app, Microsoft also is introducing a Dynamics 365 AI for Customer Service app and a Dynamics 365 AI for Market Insights app this fall, officials said on September 18.

Link: Microsoft adds two more Dynamics 365 AI apps to its roadmap
via http://www.zdnet.com

View original post

Vote on Dynamics 365 ideas


Kurt Hatlevik's avatarKurt Hatlevik - Dynamics 365 Blog

Do you know that you can influence the direction of Dynamics 365? But you may be unsure as to whether it really will make a difference. Microsoft have a site where the community can add ideas and vote on them. Go to https://experience.dynamics.com/ideas/ and create your ideas. If the idea is valid and they get enough votes, Microsoft will act and include them in their product backlog. But equally important is the ability to vote on other’s ideas.

  • Voting is the most important way to make the community voice heard on the issues that concerns the roadmap for Dynamics 365.
  • Voting gives you an opportunity to be part of the priority that affects Dynamics 365.
  • If YOU don’t Vote Others will make the decisions for YOU!

As we speak, there are 1673 ideas for Microsoft Dynamics 365 for Finance and Operations and 212 ideas for Microsoft Dynamics 365 for Retail

View original post 159 more words