Complex or Advance Query Ranges - D365

Complex or Advance Query Ranges using null, enum, expressions in D365

I came across the requirement to add custom ranges on query which cannot be handled by using the simple query add range method. So, I used query expressions to add range on query according to the requirement.

Below are some ways to use advance or complex query ranges.

We can pass values in query ranges by using strfmt

so that %1 gets the value of X and %2 gets the value of Y.

To get complete compile-time stability, use intrinsic functions to return the correct field names, as shown in the following code example.

strFmt('((%1 == %2) || (%3 == %4))',
fieldStr(MyTable, A), x,
fieldStr(MyTable, B), y)

 

Comparing with null:

We can use strfmt (%1 = = ‘ ‘) but instead it is better to use empty string function of SYSQUERY ;

qbrDate.value(strFmt('(%1 != %2)’ ),
fieldStr(InventTrans, DateInvent),
SysQuery::valueEmptyString());

Comparing with somevalue:

We there are many functions of SYSQUERY, as we already saw valueEmptyString(), other is value(), we can specify any value in it. Similarly valueLike, ValueNot etc

qbr.value(SysQuery::value(NoYes::Yes));

Using as-on-date:

 It gets the date that user input and then convert that date to string using

str inventDate = date2StrXpp(date);

qbrDate.value(strFmt('(%1 != %2)’ ),
fieldStr(InventTrans, DATEPHYSICAL),inventDate));

Using multiple enum values

enum2str

qbr.value(strfmt("%1, %2",enum2str(PurchStatus::Backorder), enum2str(PurchStatus::Received)));

any2 int is also a good option for extracting enum values in SQL as it brings the enum values in numbers

example :

qbrStatus = qbdsInvent.addRange(fieldNum(InventTrans, StatusIssue));

qbrStatus.value(strFmt('((%1 != %3) || (%1 != %5) || (%1 != %6) || (%2 != %4))',
fieldStr(InventTrans, StatusIssue),
fieldStr(InventTrans, StatusReceipt),
any2int(StatusIssue::OnOrder),
any2int(StatusReceipt::Registered),
any2int(StatusReceipt::Ordered),
any2int(StatusReceipt::QuotationReceipt)
));


Using expressions for customizing ranges on query:

QueryBuildRange           qbrDate;
QueryBuildDataSource      qbdsInvent;

qbrDate = qbdsInvent.addRange(fieldNum(InventTrans, RecId));
qbrDate.value(strFmt('(((%2 != %1) && (%2 <= %4)) || ((%2 == %1) && (%3 != %1) && (%3 <= %4)))',
SysQuery::valueEmptyString(),
fieldStr(InventTrans, DateInvent),
fieldStr(InventTrans, DATEPHYSICAL),
         inventDate));


Comments

Post a Comment

Popular posts from this blog

Batch jobs stuck on WAITING status in AX 2012

Image
Step1 . Generate incremental CIL Step2 . Check if any batch job is stuck on “ executing status ”, change its status to withhold or cancel.  Because it can be possible that all the new batch jobs are stuck on “ Waiting ” because any previous job is stuck on executing. Also, do the same for other “ waiting ” jobs Step3 . Now check the assigned batch group in your job and then check if that batch group has correct AOS server assigned and then check that if the check box named: ' Is batch server ' checked for that particular AOS server . Also, the time should be 12.00.00 to11.59.59 System administration  à Setup  à Server Configuration: either the AOS server assigned to the batch group is not marked as the batch server or else the batch group is not assigned to the batch job. System administration  à Setup  à Batch group Now run any batch job. It will not be stuck in waiting status.  
Read more

Electronic Reporting For Beginners

Image
  Basics of Electronic Reporting & Business Documents in D365 F&O Introduction: Electronic reporting is a no-code reporting tool that is completely integrated into D365.  It allows the creation of report structures directly within the platform without the need for extra software like Visual Studio.  Customization of business documents using Excel is also feasible, this is a great alternative for non-developers.  C onfigurations from the Life Cycle Services (LCS) asset library can be easily downloaded  and loaded into D365FO for use in reports and print management. Visual editors are used to create all components of the ER configuration. The language that is used for data transformation resembles the language that is used in Microsoft Excel. Data flow: Component ER supports the following types of components: Data model Model mapping Format Metadata Designing: Go to the path:  Organization administration > Workspace >Electronic Rep...
Read more

Computed column and virtual field in D365

Image
  Computed column and virtual field: Requirement: Display methods needed in entity/view Solution: There are two different approaches for adding additional  unmapped  fields beyond those that are directly mapped to fields of the data sources. 1.        Computed column (SQL query executed by Microsoft SQL Server) 2.        Virtual Field (Custom X++ code)   ·       Computed Column: The computed column method returns a T-SQL query. It hits during database synchronization and is written to the database. In runtime no x++ code is executed, instead, your T-SQL query is executed inside the database. It is mostly used for reads/exports. Performance wise it is better than virtual methods. Equivalent X++ query: select sum (amount) from consignmentProductReceiptJournalLine           where consignmentProductReceiptJournalLine.ReplenishmentOrderLine =...
Read more