Most new users get stuck with issues saying ‘Email address of the recipient was not resolved’. Like in case you want to send out an email from D365 but you don’t have the same saved in the system as a Contact/Lead or any other record. And it resulted in this the big red cross like the one below – There’s a simple setting for this in Settings > Administration > System Settings, under Email tab. You can simply flip the switch on ‘Allow messages with unresolved email recipients to be sent’ to Yes. And, now simply enter the Email address in the Recipient (To) field and let the email go! Hope this quick tip was helpful!

Introduction: One of the most common blunders often made in Data Import are importing whole lot of records without finalizing. And when you import, you realize you needed to add something more to the Import or some things were pending in the Excel file and you ended up uploading them all! Delete Imported Records: Assuming your Import was successful and you want to now just revert what all was imported, navigate to Settings > Data Management > Imports. Open the Import job and look for the option under Delete which says ‘All Records Imported to This Entity During This Import’ And the button label is self-explanatory. Once you click on it, a Delete Job is triggered once you fill in the below information And once you click OK, a Delete Job will run in the background to delete the data that was imported. Navigate to Settings > Data Management > Bulk Record Deletion and open the Delete Job that you started in Step #3 above – Also, if you selected ‘In addition to deleting imported records, delete import job history’, the Import Job record will also be deleted. So, it will be No. of records imported + 1.

Introduction: While migrating Cases, the migration of activities of type ‘Case Resolution’ is necessary. However, the complexity in migrating this increases due to the fact that when the status of a case is updated, a blank case resolution activity is created automatically by the system. This system-generated case resolution needs to be deleted as this would result in each case having two case resolution activities after migration – one system-generated and one with the correct migrated data from the source. Solution: To tackle this issue, one must follow the following steps during migration: 1. Send all Cases (no matter what the status in the source environment) to the target with their status as ‘Open’. 2. Send all related activities to the target environment. 3. Update the case status in the target environment to its status as in the source environment. 4. For cases with status ‘Resolved’, a system-generated case resolution activity will be created. 5. In your case resolution migration map, first add a step to delete the existing case resolution in the target and then insert the case resolution from the source environment. 6. Now your case with status ‘Resolved’ will have only one case resolution and that will be the one migrated from the source environment with the correct data. Conclusion: Above steps shed some light on how to preserve the integrity of case resolution activity data in your target environment during data migration.

Item Attributes are user-defined classifications that can be assigned to your items for ease of searching, filtering, and reporting. For example, a Marketing team could use attributes to help with classifying their items to aid in the grouping, sorting, and filtering for a catalog or website. The Sales team could use these same Attributes to search for Items while helping customers. To view Items and item attributes, navigate to Items in Business Central. Attributes assigned to a selected item display in a fact box on the right side of the screen. To modify or update attributes assigned to an item, a user simply selects the carrot in the Item Attribute fact box or selects Attributes in the ribbon from the Item Card. Setting up available Attributes Available Attributes and their allowed values are configurable. To add an available Attribute, a system admin or power user navigates to Item Attributes in Busines Central. From this window, a user can view, edit or add a new Attribute. The available Types of Attributes that can be used are as follows. Option– allows a list of options to be predefined for the user to select Text – allows free text entry of an attribute value Decimal – allows a numeric value (options not predefined) Integer – allows a numeric value – whole numbers only (options not predefined) Filtering by Item Attributes Back in the Item list view in Business Central, a user can filter their view by one or more attributes. To do this, select Filter by Attributes on the Home ribbon.   In the popup screen, the user can enter search criteria for one or more Attributes.   Search operators commonly used in Business Central such as @(ignore upper or lower case),*(wild card),<,>, etc. can be used. After clicking OK, the items displayed in the Item List will only be those items that meet the search criteria. To remove the Attributes filter and return to the full list of Items, simply click Clear Attributes Filter.  

Issue : Database Sync Error while applying deployable packages or Updates. Usually the Database sync error occurs at step 11:GlobalUpdate script for service model: AOSService on machine: —- Follow the steps to resolve the issue and resume the deployment. In this environment, go to Environment Monitoring –> SQL INSIGHTS –> ACTIONS tab In List of Actions, choose “Drop index” In Parameters, input “I_6640RECID” and “BANKIBANCOUNTRYACCOUNTSTRUCTURE” in Index name & Table name respectively. Choose Execute to drop the index then resume deployment.  

Issue: Void Transaction Appears in show journal in POS for Dynamics 365 for finance and Operations 8.1 When the system is upgraded to dynamics 365 finance and operation version 8.1 the user will observe that all the void transactions appear in Show journal. This bug is resolved as “By Design” means this is the expected behavior to show voided transaction with return button disabled If the voided Transactions are being returned you need to apply the APPMU general application 8.1.2 update and this will resolve the issue! On application of this update the user will not be able to return the voided transaction.  

Microsoft Teams is a cloud-based chat and collaboration platform, designed to simplify group work. Whether you prefer any chat options available across the markets, if it is not user-friendly, it won’t make any sense. For being user-friendly, the first and foremost requirement is the notifications. Of course, you would not want the hassle of logging and checking into the app every moment. So, we all rely heavily on notifications on the chat to persuade us to open it. This ensures you are updated in the real time. Such kind of wonderful notifications features is available in MS Teams. Now, having said this, let’s check out all the fabulous notification features one by one. Channel notification: To turn ON notifications for any new activity or messages on channels in Microsoft Teams, you need to follow the channel. You will not be able to follow the Team (Team is a group of personnel’s together for work, projects, etc and team are made up of channels), so you need to follow the channels within that team. Once you follow the channel, for any new message or activity in the channel you will be getting a notification (see below image). Chat notifications: You will be automatically getting a notification for one to one chat (see below image). Customize your notification settings: To further customize your notification settings, click your profile picture at the right-hand top of the application and then click Settings > Notifications. You can select, how you want your notifications from the given options (see below image). Do not disturb: As we know that if we are in a Do not disturb mode, we do not get notifications for any messages. In Microsoft Teams, we have this feature that we can still receive notifications from people who have priority access when your status is Do not disturb. You just need to add those people to Manage priority access. Click your profile picture at the right-hand top of the application and then click Settings > Privacy Mobile Notifications: Turning ON notifications on MS Teams mobile app, go to the Menu option (Hamburger button) and then click on Settings > Notifications. And then you can select from given options, how you want the notifications. To ensure you are updated in the real-time, we heavily rely on the notifications. And this is how we can manage notifications in Microsoft Teams.

Introduction: This blog explains how to rename the Dynamics 365 Sales Entity Scenario: In this we will rename Account Entity To Company. Steps: 1. Rename the Entity. Go to your solution. Select the entity and change the Display Name and Plural Name of entity. Save and Publish your Customizations. 2. Export Translations Click on Translations –> Export Translations. Extract the downloaded .zip file.  Open the CrmTranslations.xml file in Excel 3. Now we have to make changes in CrmTranslation file.  Steps: a. Unprotect all the sheets. Go to Review tab –> Click on Unprotect Sheet button Repeat this for all the sheets. Information Display Strings Localized Labels b. Go to Display Strings Sheet Highlight the whole column C Find and Replace (or press Ctrl-H) Open Options on the Replace window and ensure that Match Case is ticked You need to replace the plural names first and then the singular names. Find – Accounts, Replace with – Companies Find – accounts, Replace with – companies Find – Account, Replace with – Company Find – account, Replace with – company c.  Go to Localized Label sheet. Highlight the whole column D and repeat the steps performed in Display Strings sheet. d. Save the file. 4. Import Translation File Create .zip file. Make sure you select both the files and zip them rather than zip the folder. Go To solutions. Click on Translations -> Import Translations. Choose your .zip file and click import. Publish your Customization after Successful Import. Now you can see  changes Account entity is renamed as Company.

Introduction: In this blog we will see how to filter customer type field in Dynamics 365 to only show Accounts/Contacts dropdown. Implementation: Step 1: For demonstration purpose we will filter to only show Accounts. In the below image we can see that we have  a Customer type field which allows to choose from Contacts as well as Accounts. Note: Here accounts are called as Companies. Step 2: To display only Companies in the dropdown we register an event on Form Load. Here we are working on the Contacts form, hence we first write a JavaScript code to filter the lookup to show only companies. Below shown in the code: Code: var oContactFormCustomization = { setCustomerLookupToShowCompany: function (execContext) { var formContext = execContext.getFormContext(); if (formContext.getControl(“parentcustomerid”)) { var company = formContext.getControl(‘parentcustomerid’); if (company.getEntityTypes().length > 1) { company.setEntityTypes([‘account’]); } } }}; We add this script in CRM JS Web resource and add the library on the Contact form Properties Below shown is the Handler Properties Once this is done we can see when the form loads the scripts executes and we can now view only the Companies and not the Contacts Hope this helped!

I would like to share a consideration I take while designing Teams that you might need to make certain records shareable. I faced an issue once when users started to use Default Teams created on Business Units. And after several months, it occurred that some users from other Business Units too needed to be on that Team. And several records were already assigned to BU provided Default Teams. Scenario Priyesh belongs to Southeast Asia BU and Somesh belongs to North America BU. Some records were assigned to North America team which is the Default Team created by BU. Priyesh wanted to be in the North America team and hence the user tried to add him in that Team. So adding North America to Teams under the user Priyesh, but I get the below error – That is because you cannot add Default Teams to users in some other BUs. As a workaround, I only created a new Team and named it “<BU Name> – Shareable” team and assigned records to this team so that I know where I want the records to be visible as per my Security Roles setup. And hence, added the North America – Shared team for Priyesh. I would also like to hear your suggestions and any workarounds you may have. Thanks! 😊