Get DateTime Difference between From & to date time field in D365 F&O X++

Here is the code to get Date Time field difference between from & To date time field. Output will be difference between Days, Hours , Mints & Seconds .

 int endDuration,dayCount,hourCount,mintCount,secCount,totalTimeVal,durationVal;

 TableName #TableNme; 

durationVal =  int642int(DateTimeUtil::getDifference(#TableNme.#EndDateTime,#TableNme.#StartDateTime )); totalTimeVal = 24*60*60; 

endDuration = durationVal; 

dayCount = endDuration / totalTimeVal; 

endDuration = endDuration - (dayCount * totalTimeVal ); 

hourCount = endDuration / 3600; 

endDuration = endDuration - (hourCount * 3600); 

mintCount = endDuration / 60 ; secCount = endDuration - (mintCount *60); 

 info(strFmt("%1 - Days, %2 - Hours ,%3 - Minutes , %4- Seconds",dayCount,hourCount,mintCount,secCount));

How to execute Date Time range in X++ query

Here is the example for datetime range in Query. We are trying to achive as on date data here based on AOT and an additional range of From Date. This will help to understand the query base. 

 Query     query = new query(querystr(#AOTQueryName)); // Getting Query From AOT , 

 QueryBuildDataSource qbds = query.dataSourceTable(tablenum(#TableName)); // Adding More DB

 queryBuildRange            qbr = qbds.addRange(fieldNum(#TableName,#FieldValidFrom)); // Add Range 

qbr.value(strFmt('(%1.%2 <= DateTimeUtil::date("%3"))',tableStr(HcmEmployment),fieldStr(HcmEmployment, ValidFrom),asonDate)); // Passing Value 

Database Sync error in D365-F&O with ISV Solution

Recently I faced an issue where the Data Base synchronization for D365 F&O was throwing the error where as all the Build was successful even after move all the code from another environment. 

Here I would to mention one important thing which I was completely ignoring  was "We were using ISV solution from another party ".

Error - 

Although it was a long error log but from it you could find the below main part which will try to expose error detail. 

An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch

Solution - 

As I mentioned we were using ISV solution so it was the only reason for this Sync Failed. I had to follow the below process to make a successful Sync.

1- Go to the Local directory location "K:\AosService\PackagesLocalDirectory"

2- Got to the package folder in directory ""K:\AosService\PackagesLocalDirectory\###Package (ISV Package)"

3- Find the DLL file here .

4- Right click and open "Properties" 

5- here you will find one Unlock check box. we need to check this box and run the Sync for DB again. 

Hope this will Work for you.... :)