Microsoft Dynamics 365 and Power Platform Library

Want assurance that you never select/include fleet management modules in package creation or build all module together. Just rename the Descriptor folder from all these three locations and refresh models in VS first time to reflect the changes. <Service volume drive>:\AosService\PackagesLocalDirectory\FleetManagement <Service volume drive>:\AosService\PackagesLocalDirectory\FleetManagementExtension <Service volume drive>:\AosService\PackagesLocalDirectory\FleetManagementUnitTests

Find which data entity is obsolete after every new update. Here are the steps. For example; Customers V2 data entity is obsolete with version 8.0 For developers: Type the below in the metadata search in VSTS: type:dataentityview property:isobsolete=yes

The Microsoft team did release  platform update 12  for Dynamics 365 for Finance and Operations, Enterprise Edition 7.3. There have been few changes concerning accessibility (admin access on VMs). Starting with platform update 12 users do not have admin access to D365 VMs hosted on the Microsoft subscription. Which means: 1.     You can only log in with the "builtin\Userxxxxxxxxx" account and not the “builtin\axlocaladmin” account anymore. Prior to PU12 7.3 With PU12 7.3 2.     IIS Express is used as the web server instead of IIS 3.     IIS Express runs when Visual Studio is running  4.     Visual Studio cannot be run as Administrator anymore (you are not the local admin anymore on your development VM L ). Just double click Visual Studio shortcut or run it from start. Admin access to development virtual machines can only be achieved with following options; 1. ...

If you created a new data entity and it's not visible in your data management entity list.  Open Data Management workspace -> Framework parameters -> Entity Settings and hit the "Refresh Entity List" button

This post outlines the steps how to debug an issue which is happening in non-development or non-production environments e.g. UAT environment. 1.     RDP to your environment where you want to debug the issue, with this example I am connecting to UAT (Sandbox).  2.     Connect to SQL server a.      Get the server name from LCS database accounts b.     Use .database.windows.net to connect to database 3.     Create a new SQL sign-in that the developer can use. This step lets the system administrator maintain the security of the sandbox environment. The developer will have access to one database for only a limited time. Use the following code to create the new SQL sign-in. CREATE USER devtempuser WITH PASSWORD = 'pass@word1' EXEC sp_addrolemember 'db_owner' , 'devtempuser' 4.     Stop following services in development box a.      ...

Sample code to read an excel file, all it need file stream as a parameter. public boolean importFromExcelfiles(System.IO. Stream _stream) {    OfficeOpenXml. ExcelWorksheet         worksheet;    OfficeOpenXml. ExcelRange             cells;    OfficeOpenXml. ExcelPackage           package = new OfficeOpenXml. ExcelPackage (_stream);             int totalRows,totalCells,rowCounter,cellCounter;     if (package)    {       worksheet       = package.get_Workbook().get_Worksheets().get_Item( 1 );       cells           = worksheet.Cells;       totalRows       = worksheet....

http://www.erpsoftwareblog.com/2017/06/dynamics-365-tutorials-help-you-get-up-and-running-fast/