At times you will get an error while creating positions for employees such as this: The assignment end date must not be earlier than the assignment start date Here even if you put an Assignment end date you wont be able to create a position because the actual error is on the below form. Once you make changes to it and add date to available for assignment field, you will be able to create a position successfully Hope this helps !

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”

Import Bookings is one of the important features provided by PSA for users to do Time Entries quickly and efficiently. An issue faced while using this functionality is the Project Tasks are not imported with the Bookings Records (As Shown in the Image Below). A solution to this issue is two automated flows: To Bring the Project Tasks from Resource Requirements Entity to Bookable Resource Booking. Hence to bring the obtained Project Tasks from Bookable Resource Booking to Time Entries. Let’s Begin with the Implementation of the solution! (Flow To get Project Tasks from Resource Requirements to Bookable Resource Bookings) Step: 1 Bringing Project Tasks from Resource Requirement’s to Bookable Resource Booking. Step: 2 Update the Bookable Recourse Booking Record with the obtained project task. Now we have successfully obtained the Project task in the Bookable Recourse Bookings           Entity from the Resource Requirements, Our Next step is to Take this Project task on the Time Entries. (Flow to get Project Task from Bookable Resource Bookings to Time Entries) Step: 1 Bringing Project Task from Bookable Resource bookings to Time Entries. (Tip : It is better to check if the Project Task Field is empty or not hence we can also put a condition to do so, if the Project Task Field is empty proceed with updating the Project Task field else Terminate.) Step: 2 Get the Project Task from the Bookable Recourse Bookings. Step: 3 Update the Time Entries with the obtained Project task. Step: 4 Import Bookings and there you go you will now be able to see the Project Tasks. Hope this Helps!

Introduction : In this blog we will see how to hide tab using JavaScript. Implementation : Step 1 : Javascript for hiding tab :  Step 2 : Upload script on load of form -> ok -> Save and Publish . Result : Hope this helps

Using Microsoft flow you can automate and organize the flow of data between your Shopify and Microsoft D365 for Finance and Operation This the 1st part of 2. In this, I will show you how customers can be auto-created in D365 for Finance and Operation when it’s created in Shopify. First, log into Shopify as Admin. Navigate to: Settings -> Notifications -> Webhooks (Scroll to the end) -> Create Webhooks and select customer creation, and JSON format. We need a URL for sending customer details, which we will provide later. Now login to power apps or Microsoft automate with D365 account. Navigate to Flows -> New and select Instant from Blank. Now continue as shown in the below screenshots. Here the required URL will be generated after the flow has been saved. Click on the new step and search for Parse JSON. In Content select Body (parameter from previous steps). Now we need JSON schema for customers. You can find a sample Json return response from https://shopify.dev/docs/admin-api/rest/reference/customers/customer?api[version]=2020-04 Copy the response and select Generate from the sample in Powerapps and paste the response. The schema would be now generated. Click on ‘new step’. and search for Dynamics 365 for Fin & Ops. Click on Create record. Select the instance of the environment you want customers in and Entity name ‘CustomerV3’. Now you can place parameters from the previous step (Parse Json) in different fields such as. Mandatory fields that are required to create our customers are Customer account, Currency, Customer group, Company, Organization name. After the values are placed, click on Save at the top right corner. Now expand the first step and a URL will be there. Copy this URL to Shopify webhook and click Save webhook. Now let’s test this. Go to the customer’s section in Shopify and click Add Customer. Write the first name and last name for now and click save. Go to D365 F&O and navigate to All Customers. You should see a new customer created. In the next part, I will show how we can auto-create product in Shopify when created in D365 for Finance and Operation Thank you for reading!

In my previous blog referred here https://d365feeds.com/2020/07/08/how-do-contract-milestones-and-projects-flow-between-d365-ce-to-fo-in-project-operations/, we saw how the contract and milestones flow between CE and F&O in the integrated scenario in Project Operations. Next step is to Post the Milestones or the Approved Time entries (in case of T&M based projects) in F&O (Finance and Operations) Let’s looks at first Milestone based Invoice posting in F&O for a Fixed Bid Project: PN: How to log in to the environment is shown in my previous blog in the link above. Step 1: Login to the CE Environment to the Milestone that you need to Invoice and flip the status to “Ready for invoicing”. Step 2: The invoice is created in the CE Environment and you need to confirm the same. Upon confirming the invoice it gets integrated to the F&O Environment. Step 3: Navigate to F&O Environment and go to Project Management and Accounting à Import from staging table. This will import all the transactions available in the staging area to F&O environment. Step 4: At this juncture the Invoice is now posted to the F&O Environment. To check the same in F&O environment navigate to Project Management and Accounting Module à Pending project transactions You can see the Invoices milestone below. Step 5: Select the invoice and click on Post. This is when the invoicing of milestone is completed. This step is recommended to be performed by the Accounts Manager. Now we shall see how to Invoice Time and Material projects. Follow the steps to accomplish the same. Step 1: Navigate to CE Environment and get some time entries done on the T&M project as shown below. Step 2: Submit the time entries done by clicking the Submit button as shown below. The status of the time entries changes to Submitted from Draft status. Step 3: The project manager will now have to approve the time entries submitted from the Approvals tab. Step 4: As soon as the time entries are approved they are integrated and reside in the staging area of F&O. You then need to Import all the time entries from the staging area. Navigate to F&O Environment and go to Project Management and Accounting à Import from staging table. This will import all the transactions available in the staging area to F&O environment. Step 5: Post that navigate to Project Management and Accounting à Project Operation integration journal where all the approved time entries in CE environment get collected. Please understand that if there is an active Journal existing in F&O environment, then all the approved time entries for all the projects will be integrated to the same Journal, unless all the entries in that integration journal is approved. Step 6: Select the Journal from the below and click on the Post button from Ribbon. This will post all the transactions from the Journal, which also the final step that the Accounts manager will perform to do the invoicing. Above methods when performed can ensure that the milestones and the time entries for FP and T&M projects respectively are done. The above operations are prescribed to be done by the Accounts Manager in the company. This ends the process of Posting the Invoice in F&O Environment. The above blog is written with the best possible knowledge of Project Operations and practical experience.

In this blog, I am going to explain how to send a notification on Microsoft Teams when a record is created or Updated or Deleted in D365 CRM using Power Automate Steps involved in Power Automate: Select trigger, in my case I used CDS connector when a record is created, updated or deleted. Select trigger condition, in my case I used Update. Select entity name, in my case I used Opportunities. Select Scope, Organization. Add new step to flow. Search Microsoft Teams and select Post a message. Select Team where you want to post a message. Select Channel from team where you want to send a notification. Enter Message in message box. Click Save and check teams. Congratulations! You have successfully created the required flow. Hope this helps!!

 In D365 Finance and SCM there are lot of out of the box SSRS reports in which you have hyperlink to move to that particular record (for example Ledger transaction list). But sometimes when you update environment you might end up with no such option in you SSRS report as you can see in following screenshot.  To enable hyperlink features you need to follow following steps:- Navigate to feature management and go to all section in that Search for Report drill through links and disable this feature Search for Report PDF viewer and disable     you need to disable this feature for following limitation which you can find in screenshot. Now check desired SSRS reportNow you are able to see hyperlinks links in the reports I hope this post will be helpful to you, Thank you!

Microsoft is committed to delivering predictable service updates. These service updates will be made generally available for self-deployment approximately 2 weeks before Microsoft automatically applying the update. Some of these updates can have a lot of changes in it and this can impact any customization done on the client’s environment. Thus it becomes very important for a partner to do complete testing before any update is applied. CloudFronts is dedicated to ensuring business continuity of the client and thus have protocols set up to ensure nothing gets impacted on the client’s production environment. Following are the protocols for the same : Service Update Availability – Key points:  Each service is released by the Microsoft which has following dates criteria: Preview availability date:  When the update is in preview by Microsoft. Generally available (self-update) date: This update will be made generally available for self-deployment approximately 2 weeks before Microsoft automatically applying the update. Auto-update schedule (via LCS update settings) production start date: A date for applying the service update in the production environment. End of service date: Date from when service update is over. Referenced image: For checking the release dates for the above criteria, link as: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/get-started/public-preview-releases How Long it can be delayed for Next Service Update? The customer can pause, delay, or opt-out of an update via Update Settings in the Lifecycle Services projects. A customer can choose to pause up to 3 consecutive updates. The following is an example of a delayed update: The customer is currently on version 10.0.2. The customer can pause updates 10.0.3, 10.0.4, and 10.0.5. The customer must take the 10.0.6 update when it is available. Upcoming Schedule of Update The customer has the option to apply the update when it is convenient, or let Microsoft auto-apply the service updates based on the selected maintenance window. Customer must require to have an update no older than 4 months Critical Issues Critical issues should always be submitted to the support team via Lifecycle Services as soon as they are identified. The support staff will work with you on the resolution to the critical issue. Path for Early Service Update Scheduling Go to LCS -> Project settings Update settings Pausing the service update temporarily.  As shown in the below image, when updates resume, the designated sandbox and production environment will be updated to the latest service update before it can be paused again. HOW TO CHECK UPCOMING UPDATES FROM LCS? In update setting -> click on view the update calendar It looks like: This will help us to plan the next scheduling for service updates. According to this, we can plan the next calendar for upcoming service update CLOUDFRONTS PROTOCOL FOR TRACKING DOWN THE ENVIRONMENT DETAILS We have added the field ERP version in D365 PSA where the project lead will update the version of the production environment. After every update, it is the Project Lead’s responsibility to update this field. Every Monday we have a scheduled recurring management meeting where the CEO, Delivery Head and Practice Lead discuss the status of each project by opening a Project Overview Report developed in Power BI. The same report has the column of ERP version so that the management is aware of the client’s D365 Finance & Operations version.   CLOUDFRONTS STEPS FOR KEEPING THE ENVIRONMENT UP TO DATE For each client our support system would have one case created specifically for the updates and it will be assigned to the Project Lead. The Details of the case is as follows: Case name:  Environment update – Client name Notes:  ERP Environment version details and the next path for service update Follow-up date:  Follow-up date would be one month from the current date and till then the case will be on hold. Based on the follow up date system will automatically send the email to the assigned person so that he is intimated to work on the case. Based on this the user needs to check for updates on the LCS and follow the steps based on this document. STEPS FOR APPLYING SERVICE UPDATE – DEV / CLOUD HOSTED Key points:  Before applying the service update on UAT, service update must be applied successfully on the Build and Test Environment or Cloud-hosted environment Sequence for applying update on the environment  Build and Test Environment / Cloud-hosted environment UAT / Sandbox Production Before applying the service update, all the models should be a build-up The database must be synchronized Check if any AOT (Application Object Tree) objects are under pending changes in VSTS / TFS All the AOT objects should be checked in to VSTS Steps for applying the service update on the development environment are the same as applying to the UAT environment. Hence steps are listed on the next page. STEPS FOR APPLYING SERVICE UPDATE – UAT Go to the LCS -> Select the appropriate projectof the environment Select the UAT appropriate environment-> Click on full details Scroll down to check the latest update. In this part, we will able to see all the latest service updates. Select the appropriate service update on which we have planned to do. Click on View update. Here, we’re taking an example of moving the environment on 10.0.12 Go to Savepackage Click on Select all. Make sure all the packages are selected. Click on Save packageand then give the appropriate Service update name and then click on save the package. It will save all the hotfixes. Wait for a few moments (It can take 5-10 minutes depends on the number of packages are being loaded). After successfully saved the packages, click on Done button Go back to the environment page and then click on Maintain-> Apply updates We had given the name Service Update 10.0.12which should be shown here to apply the update In some cases, the package will not appear suddenly. What to do in such a case? Let’s see the next step on how to verify that. Go to Asset library Click on Software deployable packageand then navigate to our service package Have a look on the column – Valid. If it is not signed with the right symbol then keep patience until it is done. Once the package is validated successfully, we will able to deploy the service update to the environment. After validating the deployable package, we can see the package and just one step away for applying the service update. Click on the Apply button. TESTING – RSAT … Continue reading CloudFronts Dynamics 365 Finance & Operations Update Steps & Protocol →

We all know that Views show records based on filter criteria that is applied to the Views. But, what if there is a custom button that will change the records status and according to the Views filter criteria it should not be present in the View. The View should have been Auto-Refreshed. We can achieve this by JavaScript.  Use Case: We had a requirement where we wanted to Auto-Refresh the View as soon as the status of record is changed. We have a custom button that will change the status of the selected records but when the Status changes, it  doesn’t auto refreshes the View. We had to manually reload the page or click on refresh button on the View.  Steps: 1. When the status of the Record changes, you have the id of record then there’s a fully supported way which we can use to Auto-Refresh the View: “refreshParentGrid=Refreshes the parent grid that contains the specified record.” 2. In our case, We had the custom button which changes the status of the record. This is the code: Suppose the custom button is called as “Submit”. On clicking the button it should change the Status and also the records should not be visible in the view as the filter criteria is Status= “In Progress and Rejected” 1. The filter of the View. 2. On clicking the Submit Button, the selected record should not be visible. 3. The View Auto-Refreshed and the selected records are not visible in this View. Note: This can be used in Sub-grids of the forms also. Conclusion: I hope this blog helps you to Auto-Refresh the View.