One of my colleagues contacted me today about an issue. When he was logged into the Dynamics 365 for Operations Cloud POS and he tried to perform a “Real-Time Operation” such as resetting a password he got this error:
To reproduce it I tried to do the same, and low and behold it worked… we used the same PoS worker and we had the same Roles in Dynamics…
While he was doing some more testing i logged in to the Dynamics Server using RDP to see if there was anything in the Event viewer… Found something!
Real-time Service client library call for API ‘InvokeMethod’ method ‘UpdateStaffPassword’, language ‘sv-SE’, and company ‘usrt’ failed. Exception: ‘System.ServiceModel.FaultException`1[Microsoft.Dynamics.Retail.TransactionServices.ClientProxy.Fault]: Fault was thrown by the service for request c7f48632-52a9-447e-ba42-9d7cb4c800ba. Exception details:
Message: The language sv-SE is not supported by Microsoft Dynamics 365 for Operations. For a list of supported languages, see Microsoft Dynamics 365 for Operations Online. (Fault Detail is equal to Microsoft.Dynamics.Retail.TransactionServices.ClientProxy.Fault).’.
The language sv-SE is not supported by Dynamics 365 for Operations… that’s better… now I know where to look. My browser was using english and my colleague was using swedish. We changed it to look like this by switching the order and moving English to the top…
… it worked !!!
That is all for today
Today I am setting up the mobile warehouse app in Dynamics 365 for operation… there is a very nice Wiki article here with the walkthrough but I am doing a slightly condensed version.
- Go to the azure portal. In Azure Active Directory – App Registrations create a web application for the warehouse portal
Application Type: Web app/API
Sign-on URL: https://[theURLforyourdynamicsinstance]/oauth
- Open the application to edit it
- Verify Application ID. If you create the Application in the new new portal it will auto generate an AppID which is random. If you use the old portal to create the application you will have to add the App ID URI. Make sure that this URI is NOT your Dynamics 365 for operations URL because this will break for instance Excel Add-in and Management Reporter. For more information look here
- Note: the next step did not work from the new portal so I had to perform it from the old portal.
- Go to the old Azure Portal – Active Directory – [Your AD] – Applications and select the application you created in the previous step
- Under Permissions to other applications click add application and add Microsoft Dynamics ERP
- Add the following permissions
Access Dynamics AX online as organization users
Access Dynamics AX data
Access Dynamics AX Custom Service
- In the new portal in the application permission click keys, enter the name for your new key and set a duration. When you click save you will get the key. Please remember to copy and save it some where because it will not be visible later.
- Now you need to save the ClientID (Old Portal)/Application ID (New Portal) for later.
- Log into Dynamics 365 for Operations and go to System Administration – Users and create a new user (in my case called WMAPP. The email address can be anything since it will never be used. The user needs these roles
Warehouse mobile device user
- Now we need to associate the user to the AD Application which is done on System Administration – Setup – Azure Active Directory applications. Here we paste the App ID/ClientID from before and select the user we created. Click Save and you are done.
- Install the App from app store and enter these settings:
1. Azure Active Directory ID: AppID/CleintID from step 9
2. Azure Active Directory Client Secret: The key from step 8
3. Azure Active Directory Resource: Your Dynamics 365 URL
4. Azure Active Directory Tennant: https://login.windows.net/yourADtennant
5. Company: Dynamics 365 for Operations Legal Entity
Vi har i veckan varit i Seattle och besökt Technical Conference 2017 för att se var Microsoft har på gång vad det gäller Dynamics. Vi har dagen till ära spelat in ett extra avsnitt där vi pratar lite om våra reflektioner på konferensen. Det kommer garanterat att komma med så småningom.
I avsnitt 4 av DynamicsPodden går vi igenom rapportering i Dynamics 365 for Operations och tittat på vilka likheter och skillnader som finns jämfört med AX 2012. Vi tittar på Power BI, Management reporter och Reporting Services
Då var vi tillbaka med ett nytt avsnitt av DynamicsPodden. Denna gång har Emelie, Jonathan och Johan samlats för att prata om mobilitet. Vad betyder egentligen Anywhere, Anytime? Hur ser upplevelsen ut på mobila enheter, hur är kompatibiliteten med andra browsers och vad behöver vi fundera kring när det gäller säkerheten?
Håll till godo
I am so sorry about the click bait title… I could not resist
Todays adventure consists of troubleshooting why Report Editor and Workflow Editor stopped working in our Dynamics 365 for Operations environment. First som history:
This all started in one of our environments where we noticed that Report Designer for Management Reporter (Financial Reports) was not working… after some troubleshooting we called MS Support and did two days of troubleshooting I got the suggestion to try this in another environment (I am a little annoyed that I did not do this before) and of course it worked. Well, that did not really provida a lead to the root cause. One day later I got a request to configure PowerBI in the environment where it worked and later that day once again tested in the “working” environment and low and behold… it did not work!!! What the_____? This got me thinking about what could have caused this… I installed PowerBI… could it be… Yes it could.
I remembered that I had read in the description of the PowerBI configuration that there was a caveat in the configuration of the Azure AD Application:
“App ID URI: This value is mandatory, but isn’t required for the workspace integration. Make sure that this App ID URI is a mock URI like https://contosoAX, since using the URL of your deployment can cause sign-in issues in other AAD applications such as the Excel Add-in.”
So I went back to Azure AD and I had unfortunately not done this…
I changed this in both environments and… Voilá… it worked.
Note: This has been changed in my original post on PowerBI
Was looking today for a way to test mobile workspaces in Dynamics 365 for Operations (still no good abreviation). This is a bit hidden.
To be able to create a mobile workspace you log into D365O. Once you have logged in you, goto the address bar in your browser and add &mode=mobile to the end of the address and press enter.
Go to the module where you want to create the mobile workspace and click the settings wheel in the top right corner and a new menu item is visible
Click mobile App menu item and then click + Add
In my example I am in the Project module. I click Add to create a mobile app
I click + Add Page and give it a name and a description and click Done
Click + Select Fields to add which fields to view. You add fields by clicking on the plus on each column and click Done when you are ready.
Click Done and Publish workspace to finish the Mobile Workspace.
To test your Mobile workspace, install the Microsoft Dynamics 365 app from Google Play Store eller från Apple App Store, add the URL to your Dynamics 365 for Operations tenant, log on with your Azure Active Directory account and test your workspace
Today I helped two of my colleagues setting integrating Power BI for Dynamics 365 for operations. There are a couple of guides online which I have used to create this post, but I thought I would create one from my experience.
There are a couple of main steps we need to go through:
Create a Azure AD Application
Configure Dynamics 365 for operations for Power BI
Configure Power BI
Configure your workspace
Create a Azure AD Application
There are two ways of doing this… you can do it using the Power BI Developer registration tool or you can do it directly from the Azure Portal. We did it from the Azure Portal like this:
- Log into the Azure potal… You can use both the old and the new one
- Goto Azure Aztive Directory and select your Azure Active Directory Instance
- Go to Applications/App Registrations
- Create a new application with these settings:
- Name: ChooseYourName
- Application Type: Web app/API
- Sign-on URL: https://theadressforyourdynamics365foroperationsinstance/oauth
- App ID URI:
https://theadressforyourdynamics365foroperationsinstance Anything EXEPT https://theadressforyourdynamics365foroperationsinstance . You can for instance use https://DynamicsBI, it only has to be unique for each Azure AD Application
Edited 27/1 2017
- Reply URL: https://theadressforyourdynamics365foroperationsinstance/oauth
- When this is created you will get a Client ID/Application ID and you will create a key. You need to save these because you will need the later. Note that the keys are only visible when they are created, Once you leave the page and go back you cannot see them again. If this happens and you have not saved it you can simply create an new one.
- Once you have set up the application in Azure ID you will need to give it some permissions. This is where we got stuck because in one of the guides there was a screenshot which showed to few permissions and it simply did not work. You add the application Power BI Services and give it the correct permissions. We used the following permissions:
- View User Groups
- View all Groups
- View All Reports
- View content Properties
- Read and Write all datasets
- View All Datasets
- View All Dashboards
Configure Dynamics 365 for operations for Power BI
- In Dynamics 365 for Operations, go to System Adminstration – Power BI
- You need to Enable the configuration and then you change these values
- Azure AD Tennant (this you will find in the Azure Portal)
- Client ID (you saved it above)
- Application key(you saved it above)
- Redirect URL: ps://theadressforyourdynamics365foroperationsinstance/oauth (This one is incorrect and will not work… ever… I do not understand how there can be an incorrect default value)
The other values are correct
Configure Power Bi
- Every user that is going to use Power BI (more or less every user that is usign AX) will need at least a Power BI free License. As the name implies it is actually free and you addit in the Office 365 Admin Portal. Once you have added the wou will have to do this for every user:
- Log into Power BI (https://powerbi.microsoft.com)
- Click Get Data in the lower left corner
- Click Services – Get
- Click Get it now on each of the three (for now) AX Apps
- On each of the Apps enter the URL for your AX instance (https://theadressforyourdynamics365foroperationsinstance ) and flick next. If you get prompted for authetication select OAuth2
Configure your workspace
- Log into Dynamics 365 for operations
- Go to the Workspace called Cost Administration
- Scroll to the right and click on the Power BI pane
- If this is your first time you need to authorize Power BI. Click the link, log in using your credentials and approve the permissions.
- Return to the Dynamics Tab and click close
- Select the Power BI tiles you want from the Tile catalog and click OK to add them to your workspace
This should be it… Business Intelligence glory!
I detta andra riktiga avsnitt av Dynamicspodden pratar vi om en av de största förändringarna i Dynamics 365 for Operations, nämligen gränssnittet. Vilka är fördelarna med ett webgränssnitt? Hur kan jag skapa tredjepartsappar mot dataentiteterna i AX och hur kan jag integrera externt data och Power BI rapporter direkt i gränssnittet.
I studion: Emelie Jurstrand, Jonathan Bucht och Johan Persson
/Emelie, Jonathan och Johan