Introduction: In this blog, we will see how to resolve HTTP Error 503 – The service is unavailable in Microsoft Dynamics 365 Finance and Operations Details:  For resolving these kinds of errors, we have 2 solutions as of now. One is to do from the front end that is LCS and the second is to do from the back-end that is from Visual Studio From LCS: Reset the IIS from the LCS. Steps: 1.     Go to LCS, login 2.     Select the respective project, full details   3.     Go to Maintain -> Restart service       4.     Select IIS and confirm it     5.     Wait till the service is being restarted                       From Visual Studio: From the back-end, open the VM and follow the below steps: 1.     Login to VM 2.     Open the Visual Studio 3.     Go to Dynamics 365 tab 4.     Click on Restart IIS Express That’s it. Build the project and go to the frontend and check the output how it looks like. Thanks for reading and stay connected with us for more updates!!! Jagdish Solanki | Senior Technical Consultant | CloudFronts Business Empowering Solutions Team “Solving Complex Business Challenges with Microsoft Dynamics 365 & Power Platform”

Introduction:  In this blog, we will see how we can synchronize the database through PowerShell in Microsoft Dynamics 365 Finance and Operations Steps:  K:\AOSService\webroot\bin\Microsoft.Dynamics.AX.Deployment.Setup.exe -bindir “K:\AosService\PackagesLocalDirectory” metadatadir “K:\AosService\PackagesLocalDirectory” -sqluser “axdbadmin” -sqlserver “.” -sqldatabase “AxDB” -setupmode “sync” -syncmode “fullall” -isazuresql “false” -sqlpwd “*” -logfilename “H:\MSSQL_LOGS\AxDB_log.log” Example: K:\AOSService\webroot\bin\Microsoft.Dynamics.AX.Deployment.Setup.exe -bindir “K:\AosService\PackagesLocalDirectory” metadatadir “K:\AosService\PackagesLocalDirectory” -sqluser “axdbadmin” -sqlserver “.” -sqldatabase “AxDB” -setupmode “sync” -syncmode “fullall” -isazuresql “false” -sqlpwd “AOSWebSite@123” -logfilename “H:\MSSQL_LOGS\AxDB_log.log” Thanks for reading and stay connected with us for more updates!!! Jagdish Solanki | Senior Technical Consultant | CloudFronts Business Empowering Solutions Team “Solving Complex Business Challenges with Microsoft Dynamics 365 & Power Platform”

Introduction: In this blog, we will see how to create factbox of workflow history of purchase order in Microsoft Dynamics 365 Finance and Operations Details:  Well, Factbox is a very pretty cool feature available from the earlier version AX 2012. It is very easy to achieve in Dynamics 365 as well.  Here we will see how easy it is and steps for that.    As shown in the above image, we will be going to create factbox for the “Tracking details list” Steps:  Create the solution in Visual Studio and project for that. We’ll be required four objects mainly that is one display MenuItem, Table, Form (on which to display factbox), another Form (factbox). Reference attached below: 1. Table For displaying workflow history, we need to create the extension of table WorkflowTrackingStatusTable and create the normal relation and its relevant properties as 2. Factbox Now we are required to create the factbox of workflow history. For that we will use the effortless technique, where we will duplicate the standard form “WorkflowStatus” and will name as CFSPurchTableWorkflowHistoryFactBox (give name as per your naming convention standards) After duplicating and renaming the form, we need to change the pattern as “custom” After applying the custom pattern, delete the NavigationList which is not required in factbox, and do visible false ActionPane and PanelTab After that create the new Grid and assign the data source to it in the property and put all the required fields to show in factbox 3. Display MenuItem We will attach the created factbox form to the display menu item and relevant label “Workflow history” 4. Base form Base form we call it as where we will attach the factbox. Here it is purchase form. Go to Parm section and create a new part and give it a relevant name and its properties Properties:  Data source: Attached data source with which workflow history is connected Data Source Relation: WorkflowTable.RelationName Name: Part name That’s it. Build the project and go the frontend and check the output how it looks like. Conclusion: It results as (we can scroll left and right to see all the tracking details list) Hurray, How pretty it looks like! In the above example, we have seen how we can develop factbox in Microsoft Dynamics 365 Finance and Operations.   Thanks for reading and stay connected with us for more updates!!! Jagdish Solanki | Senior Technical Consultant | CloudFronts Business Empowering Solutions Team “Solving Complex Business Challenges with Microsoft Dynamics 365 & Power Platform”

Introduction: From the version 10.0.10 Platform update 34, Microsoft has added a new feature Message::AddAction() which is shown in the message bar.  Details: Message API associated with display or action menu items, which is visualized as a hyperlink/link button.  It is linked with a single record at a time, called single action. In below taken example, we will show sales order is navigated to the form SalesTable from the message bar. For testing it, we’ll create the runnable class also know as job in AX 2012.  class CFSMessageAPI { public static void main(Args _args) { SalesTable salesTable = SalesTable::find(‘SH-000121′); MenuItemMessageAction actionData = new MenuItemMessageAction(); actionData.MenuItemName(menuItemDisplayStr(SalesTable)); actionData.TableName(tableStr(SalesTable)); actionData.RecId(salesTable.RecId); str jsonData = FormJsonSerializer::serializeClass(actionData); int64 messageId = Message::AddAction(MessageSeverity::Informational, “Sales order details”, salesTable.customerName(), MessageActionType::DisplayMenuItem, jsonData); } } Let’s see how it works,  In my case it’s showing Mitchell. Click on the link.  After clicking on the action link, it is navigated to the sales order record form as shown in the above link.  Hurray, How pretty feature is released !!! Conclusion: In above example, we have seen how Message API is routed to the record. Thanks for reading !!!

In this blog article, we will see how we can create a project and deploy a dynamic 365 operations environment using Lifecycle services. Prerequisites: Azure Subscription Lifecycle Service Account Step by Step approach: Environment Setup  Azure Subscription: Login to the Azure portal using credential use below URL and buy Pay-As-You-Go subscription as LCS will consume more resource and if we choose start free option it will give error later when we deploy the VM. “https://portal.azure.com/” Once we done with the subscription go to the subscription tab and select the Access Control option and create a role select the role as the Contributor and Add a user select the user as the “Dynamic Deployment Services.” We can now login to the Lifecycle Services remember we should login in LCS using the account which has the admin access to the subscription. After login we can see the following screen. The first step in LCS is to create new project so click on (+) sign to create new project.  Once we click on (+) sign we’ll have different option the option may vary as per the version of LCS you are using, here we are setting up environment for development and learning purpose select the “Migrate, Create Solutions, and Learn” option. Enter the project details and click on the create option. All the information is related to the how you want your project settings to show and the methodology option let you select what you want to shows up on the default project information that shows up in lifecycle services so the migrate and create dynamic 365 for operation solution give you these options.  Once we click on create we’ll land to the life cycle project homepage Access the Azure subscription:- Scroll to the right and click on the project settings We are accessing the azure subscription so click on the Azure connectors options we’ll see the following screen. The first step is to authorize your organisation in the LCS click on the authorize link. Linking LCS to Azure subscription click on the Add option and set the required option make sure the subscription id is same as you have in the azure portal as we may have multiple subscription set so keep in mind to use correct subscription. Once we fill the required details click on the next. Once we click on next we’ll required to authorize the user to the subscription or we can download the certificate and upload to the azure portal by going to the Subscription > Management Certificates > Upload then upload the certificate that we have downloaded. Select the server environment region for LCS. Now we can see the azure connection in the project setting we got Azure subscription id that is showing . Deployment for the virtual machine In newly created environment go to the Project and in environment tab click on the (+) sign Once we click on (+) sign we’ll application platform option choose the latest application and platform version. Select the environment topology here we are selecting Demo environment Specify the Deploy environment setting by clicking on the Advance setting option Choose the below option and leave the other settings as default Click on the next. We can set size of the virtual machine of our choice it’s fine to keep the default settings and go ahead. Once confirm and deploy the VM deployment will start, usually deployment will take 3 hr. So, this will create the D365 Operation Environment for us. In next blog we’ll see how to setup the post deployment configuration setting for the environment

Introduction: In D365 Operations, when we create a workflow for Purchase Order we face a formatter error related to Time zone. This error is caused due to conflict as same time zone specified twice for a legal entity. First for the legal entity and second time for the address. In this blog, I will tell you how to resolve it. Solution: Go to Organization Administration -> Legal Entities In Address Tab, select More options -> Advanced In General Tab, Edit the Time zone to a different time zone.

Introduction: Deployment of Power BI to Dynamics 365 for Finance and Operations is done by Embedded Power BI in Dynamics 365 for Finance and Operations. Configurations of Power BI in operations: Configure your LCS project within Dynamics 365 for Operations Navigate to System Administration –> System Parameters –>Go to Help Tab Here you will be asked to Connect to Life Cycle services. This operation is mandatory, it enables Dynamics 365 for Operations to established a trusted connection to LCS using your user credentials. Click on “Click here to connect to Lifecycle Services” On successful connection, you will be able to choose a set of LCS projects from the drop down menu. Select the LCS project Enable Power BI: Register Dynamics 365 for Operations deployment as an web app. 1. Login to you Power BI account 2. There are some fields we need to fill in: AppName (e.g. “D365PBI”) AppType (Server-side Web app) Redirect URI (this will be your instance URL with “oauth” at the end. E.g https://D3651611aos.cloudax.dynamics.com/oauth) Home Page URL (This will be your instance URL. E.g https://D3651611aos.cloudax.dynamics.com/) 3. Choose APIs to access 4. Then hit “Register App”. This will generate a Client ID and a Client Secret which we are going to input inside D365. 5. Keep this window open, we need to copy paste the keys into D365. Deploy Power BI Files: Navigate to System Administrator –>Deploy Power BI Files .Click on Deploy Power BI Files Here you will be asked to Authorize Power BI, Click on Authorize Power BI. Click on Deploy Power BI Files

Introduction: In this blog we shall see how to Issue and redeem Gift Card in Dynamics 365 for Finance and Operations. Issue Gift Card: On POS go to Sales. Go to Action and select Gift Card. Click on Issue Gift Card. Enter the Gift Card Number. Enter the Amount for gift Card. Select any Tender to pay. You Can check the details of the Gift card under Gift card in Dynamics 365 FOE. Redeem Gift Card: On the Transaction Screen select the Products. To redeem the gift card select on Pay gift card. Enter the Gift card number. You can check the balance by clicking on check balance. Proceed to pay. You can manually enter the amount and remaining due can be paid by other mode of payment. You can check the details of the gift card under gift card in Dynamics 365 FOE.