Microsoft Dynamics 365

WorkflowTable            workflowTable; WorkflowVersionTable     workflowVersionTable; WorkflowElementTable     workflowElementTable; WorkflowStepTable        workflowStepTable; WorkflowAssignmentTable workflowAssignmentTable; while select workflowAssignmentTable     join workflowStepTable     where workflowStepTable.RecId == workflowAssignmentTable.workflowStepTable     join workflowElementTable     where workflowElementTable.ElementId == workflowStepTable.ElementId     join workflowVersionTable     where workflowVersionTable.ConfigurationId == workflowElementTable.ConfigurationId         && workflowVersionTable.Enabled == NoYes ::Yes     join workflowTable     where workflowTable.RecId == workflowVersionTable.workflowTable     && workflowTable.DocumentTableName == "LeaveRequestHeader" {     info(strFmt( "%1" , workflowAssignmentTable.UserValue)); }           

Multi Select Lookup in SSRS Report in D365 Description:-  Here we will create multi select lookup in ssrs report so we can select multiple data from lookup. Here I have given sample demonstration for how to generate multi select lookup in ssrs report. First, you must create contract class for that and create method for parameters. Contract Class: - [DataContractAttribute, SysOperationContractProcessingAttribute( classstr (SampleUIBuilder))] class SampleContract implements SysOperationValidatable {     List   ListItemId; [DataMemberAttribute( "Item Id" ),AifCollectionTypeAttribute( "Item Id" , Types ::String),        SysOperationLabelAttribute( literalStr ( "Item Id" ))]        public List parmItemId( List _ListItemId = ListItemId) {               ListItemId = _ListItemId;               return ListItemId; } } //For validation parameters,     public boolean validate()     {         boolean              is

Cache Lookup Caches are used on both the client and the server. It increases the performance, the ax will get data from the cache instead of doing round trips and DB calls. So for each table, it's good to use cache lookup property.Microsoft Dynamics Ax run time manages the cache by removing old records when new records are added to the cache. Client Cache A Client-side cache can be used only by the client. The client cache is used when a select statement is executed from the client tier. If no records are found in the client cache, the client then searches in the server cache for the records. If the record isn't located in the server cache, it will retrieve from the database. The maximum number of records can be maintained in a client cache is 100 records per table for the selected company. Server Cache A server-side cache can be used by any connection to the server. The server cache is used when a select is executed on the server tier. If no record found in th