Many times you find issues like one of your users are unable to set up their Office 365 Email account in Microsoft Outlook or Outlook suddenly stopped working or it is taking too much time to setup account after the credentials are entered. What will be the steps you will be performing at that time to resolve that issue? The best and very simple solution, in this case, would be to run Microsoft Support and Recovery Assistant. I was facing one similar issue one day. Let me go through the steps below which I performed and the issue what I found and how easy it became to resolve the issue. Before I proceed, let me provide you some info on SARA tool and how to install. Microsoft Support and Recovery Assistant work by running tests to figure out what’s wrong. It can fix many problems or can tell you how to fix them. SARA can fix several issues such as Office setup, Outlook (for MAC as well), Exchange Online, OneDrive for Business, etc. Installing SARA: Go to Outlook Support Center, click Download now. Click RUN when you are prompted on your system and then click Install. SARA will get downloaded. Click on I Agree after you have read the service agreement. And now you are ready to use the tool. How I resolved the Outlook issue for one of my users? Open SARA application or if you had just installed select Outlook and then click NEXT. You will be asked to confirm that you are on the affected machine, select Yes and click NEXT. You will be asked for the user credentials, enter the Office 365 account credentials and then click NEXT. After the validation process, the scan begins automatically. Below is the screenshot my Outlook scan results on the affected system. You have seen how I got the issues found with the help of SARA. So, in this case, the issue was that the “Use a proxy server for your LAN” option was checked on this system and I fixed that. After doing the same my issues got resolved. What if you are unable to understand the issues after scanning? SARA also provides an option to view the detailed report of the issue and if you are unable to understand the issue, you can always raise a support ticket with Microsoft. SARA also provide you with the feature of sharing your scan results to Microsoft. So, if you are working with a Microsoft support engineer, this option is very helpful. What if I am using other email system and not Office 365 with Microsoft Outlook App? Sara also provides support to accounts who don’t have Exchange Online, instead, they are using some other email system with Microsoft Outlook app. You will be able to authenticate and start the scanning for your Outlook app and can view the issues or detailed report. The only difference is, you won’t be getting the option to share your data with Microsoft instead you can share the logs with the person who is responsible for your Outlook issues, for example, your helpdesk person.  

Introduction: Here, I will demonstrate how a user can add data into reports by themselves from the Request Page in Business Central. Pre-Requisites: Microsoft Dynamics 365 Business Central Steps: Create a report and in the Report Page section enter a text variable which you want to display in the report. requestpage { layout { area(Content) { group(General) { field(Note; Note) { ApplicationArea = All; MultiLine = true; } } } } } 2. Insert this variable on the report layout where you want it to be displayed. 3. Click on the Action and the Request Page opens up where the data in the variable to be displayed on the report can be seen/entered. The user enters the data and clicks on Preview. The data can be seen on the report. Conclusion: Thus, this way user can enter data in report from the request page.

Problem Definition: As soon I upgraded my PSA version from V2 to V3, I saw that the role field got deprecated. Not only that, it was removed from Schedule (WBS in V2). We now had the functionality to directly assign resource to the task against having assign role. The projects that got migrated from V2 to V3 were all tagged with the resource named “Auto-Developer” and were with the roles, but, was not advisable to go the deprecated way. We now as an organization, heavily dependent on our day-to-day activities had to change the way we work and had to understand and reframe the working methodology for the following things: How to take care of the tasks that we need to make it Non-Billable Where to assign roles and learn to assign Resources instead. Solution: The above problem was not an easy cake to eat. The impact went all the way to Schedule Board and we need to redesign the way we allocate on tasks, since, I started seeing duplicate tasks on schedule board, one with Role and one without Role. I had to change the view query to reflect the tasks without role and match the remaining hours to the previously assigned hours on the task. Now this became a major challenge. We had to export all the bookings from the system and delete the previous allocations on the task with role to the task without role. This would then match the remaining hours to allocate on the task. The next things I did to make the tasks be treated as Non-Billable was to add the Column in the Schedule named Category, Wherein I added a Category named “Non-Billable”. This category was made Non-Chargeable. This is the Transaction Category which can be added from SettingsàTransaction Categories. I added a Calculated Field on the Project form then to calculate the Billable Hours which excluded this Non-billable Category task to see the correct Billable estimate of the project. BI Team in your organization will now need to change the reports adjusting to the above criteria to reflect the correct data. This blog reflects my personal findings and based solely on my experience of using PSA for last 3 years. For those who are looking for a platform that can track and manage the entire procedures of sales and project managements, I would highly recommend them to try Microsoft dynamics 365 for project service automation.  

This being an obvious approach to how Dashboards are by default seen by all. And how you can disable/hide for users. Even for D365 System Administrators! Unlike usual forms, view or other records, And Deleting the Dashboard isn’t an option. Enable Security Roles way So a simple trick is to remove entire access from Enable Security Roles Make sure Display only to these selected security roles And then just untick if you want to provide no access to anyone Hope this works!

Introduction: While I was testing InterCompany Setup, I faced an issue probably a limitation of the CRONUS standard license which comes with standard NAV/ BC On-Premise installations. Whenever I created new multiple Companies in NAV, I got an error ‘Your program License doesn’t permit support maximum N non-demonstration companies‘. Pre-requisites: Microsoft Dynamics NAV 2018. Microsoft Dynamics 365 Business Central. Solution: I faced this error when I restarted NAV Client after creating a non-evaluation company. Thus, I cannot remove the company from front-end. I tried using Microsoft Documentation and found that it was actually possible (YAY!! 😁). Refer https://docs.microsoft.com/en-us/dynamics-nav/how-to–delete-companies. Instead, it kept ruining things more. The Server Instance would stop without any errors and NAV Windows Client would infinitely work trying to connect to the workspace. Finally, I found that using Windows Powershell with NAV Management module where it was possible to delete the Company from the back-end. NOTE:  1. The database shouldn’t be in Single user mode. 2. The NAV Server Instance should be in RUNNING state. Powershell Commands and Outputs: Recreating the error by creating new companies. Creating a new Company!   Changing to the new Company! Importing the NAVAdmin Powershell module which comes in the package when you install NAV/ BC On-Premise. Getting the list of Companies on the NAV Server Instance using PowerShell Removing the Company for a particular NAV Server instance Conclusion: I tried going into single user mode to delete the company from NAV Windows Client but it didn’t work  

Introduction While working with workflow, we can map the same data type field while creating or updating a record. But there was an issue with optionset mapping. Description: I have used workflow quite a lot time but recently I was mapping an option set with another option set which has the same value, but it was not showing the value. I found that due to local option set not allowed to map. As you can see in the below screen it is not showing the field to map. To overcome with this, we need to perform the below three steps 1.) Create a global option set 2.) Create local option set using the global option set on source record 3.) Create local option set using the global option set on target record Once above field is created you will able to see the mapping field Note: 1.) Since we are creating another field, make sure that you have kept the history value of old record. 2.) Do not delete the field while creating new field mapping Conclusion: Hope this helps you to map optionset using workflow.

Introduction: What is Admin Center in Business Central on Cloud? How to use it and what are the implications? Admin Center is one of the newest features of Business Central On Cloud. Here, you can manage your environments and performs tasks related to your environment. Demonstration: To goto Admin Centre, visit the URL https://businesscentral.dynamics.com/<TENANTID>admin To visit the Admin Centre you should have the Global Administrator permission in Office 365. Environments: Here you can see a list of Environments. You cannot Create to Delete the production environment. Only you can Create or Delete Sandbox Environments. Viewing details of the Environment: Click on the Environment Name: Upgrade Settings: You can set the Time to auto upgrade your Tenant Environment. Copying of Production on Sandbox: Notification Recipient: Notification Recipient is a person to notify in case there are some things to notify the user about. I thought it was with regards to Sandbox Upgradation but I didn’t get any updates during, before or after graduation. In fact, even when the Sandbox was not working it did not send an email. Telemetry: Telemetry shows the logs of Events that were triggered and shows the list of errors. Telemetry also shows which Codeunits were executed and at what time. This is a cool tool to know if there are any errors occurring when running your sandbox/production. It is like an Event Log for Business Central Conclusion: Thus using Admin Center you can get details about the Business Central. You can manage different environments, copy Production environment into Sandbox and Monitor the environments.

This functionality helpful to correct posted Sales invoice if user make mistake or want to do any changes. You cannot correct posed Sales invoice which are partially or fully paid. In search bar enter Posted Sales Invoice and chose the related link. Select and open Posted Sales Invoice which you want to correct Click on correct button on Posted Sales Invoice form. Once you click on correct then you will get below pop up. Choose yes to continue. New Sales Invoice with same information will be created. Make the changes whichever are required and click on post button to post Sales invoice. In Posted Sales Invoices form, you can check new posted sales invoice. Choose Show Corrective Credit Memo to view the posted Sales credit memo that voids the initial posted Sales invoice.

Transfer order mainly use for Transfer inventory from one location to another location. Below are the steps to create transfer Order In the Search box, enter Transfer Orders, and select the link Click on New button to create new transfer order. Select the Location in Transfer from Code field from where you want to ship the Inventory Select the Location in Transfer to Code field from where you want to receive the Inventory. Direct Transfer: If select yes then the transfer does not use as in-transit location. When you transfer directly, the Qty. to receive field will be locked with the same value as the quantity to ship. Select the Item, quantity on Transfer order lines. If Direct transfer is no then Select the Location in In-Transit Code field which is used for mainly material is shipped from one location but not received in another location. On Action tab, click on post button to ship the Inventory from one location. Select ship in message Box and click on OK. You can check Quantity which are shipped in Quantity Shipped field. Then again click on Post button to receive the inventory in another location. Select Receive in message box and click on OK. You can check transferred shipment in Posted Transfer Shipments. You can check transferred receipts in Posted Transfer Receipts. Conclusion:  Transfer orders involve posting items as shipped from one location and posting them as received at the other location.  

Introduction: In Microsoft Teams we create several teams, managing teams and channels is also very important so that you can work in a compliant way. When you create a team a SharePoint site and an Office 365 Group is also created.  With the increased use of O365 Groups, admins and users must have some way to clean up unwanted or unused groups. Here comes the need of setting up Team or Group Expiration Policy from Azure Active Directory and as you know Teams is based on Office 365 Groups, it is influenced by Group Expiration Policy. In this article, we will see how we can effectively manage teams or groups with the help of Group Expiration Policy. Let’s get started: 1. Go to Microsoft 365 Admin Center > Azure Active Directory. 2. In Active AD, go to Groups > Expiration Policy. 3. You can then set an expiration policy for a group by providing Group Lifetime. 4. You can set a default group expiration as 180 or 365 days else you also select custom and enter the number of days as per your requirements, but it should be more than 30 days. 5. When the expiration policy is in place, once a group ages to 30 days before their lifecycle period lapses, group owners receive notifications for renewal (3 notifications are sent on 30, 15 and 0 days respectively). If it is renewed the lifecycle extends for a defined period and if not renewed O365 soft-deletes the group when it expires. If there are no owners of that group, you can provide an email Id of someone who will be receiving the notifications. Note – Owners can recover the soft-deleted groups during the next 30 days. 6. Select the groups and save the policy by hitting the Save button. FAQ’s:- Is Group Expiration Policy available with a free or basic subscription of Azure AD? Answer – Group Expiration Policy is a premium feature and is only available with Azure AD Premium subscriptions. What happens if a Team or Group owner fails to check the expiry notifications? Answer – Teams also shows the expiry information on Teams settings. Open the team for which you are the owner and select manage team and then go to settings. At the bottom, you can see Team Expiry option. In addition,  If O365 soft-deletes the team or group, owners have 30 days to recover the group and when a team is expiring, a warning triangle is displayed alongside the team name which is only visible to team owners. Conclusion: In this way, you can effectively manage your team or groups. The policy helps to remove inactive groups from the system and make things cleaner.