Following are the operators that are used in ConditionExpression (if using through SDK) or FetchXML queries. FetchXML Operator ConditionOperator Description like BeginsWith The string occurs at the beginning of another string. between Between The value is between two values. like Contains The string contains another string. not-like DoesNotBeginWith The string does not begin with another … Continue reading Dynamics CRM 365 Online Fetch XML Operators
Retrieving Dynamics CRM entity records with Columnset(true)
If you are retrieving Dynamics CRM entity records for any update, always avoid loading all columns using Columnset(true) parameter. This will be a bad practice not only from performance point of view but also, it will update all attributes causing either plugin/workflow to be triggered or anything weird can cause data inconsistency. This would be … Continue reading Retrieving Dynamics CRM entity records with Columnset(true)
Delete Batchjob History from SQL Server – AX2012 R3
Batch job history in AX2012 R3 is consuming too much space. Here is the script to delete old history records from database Use MicrosoftDynamicsAX declare @lastweek datetime declare @now datetime set @now = getdate() set @lastweek = dateadd(day,-7,@now) Delete from BATCHCONSTRAINTSHISTORY where BATCHCONSTRAINTSHISTORY.BATCHID in (select BATCHID from BATCHHISTORY BH join BATCHJOBHISTORY BJH on BH.BATCHJOBHISTORYID = … Continue reading Delete Batchjob History from SQL Server – AX2012 R3
Common Data Service (CDS) vs Azure SQL Database
CDS Azure SQL Database The main benefit of the CDS is that it's simple to use. Non-IT guys can use it very easily to design their database On the other hand, Azure SQL needs to be managed by someone who has knowledge of relational database and SQL Queries CDS tables can be designed through web-based … Continue reading Common Data Service (CDS) vs Azure SQL Database
Dynamics 365 v9 with Power BI
Recently my old Power BI reports stopped working when the Dynamics CRM (Dynamics 365) was updated to v9.0 and Power BI was updated in July 2018. Power BI has released some changes in OData endpoint connectivity. The issue can be resolved by changing the connection from Advanced editor from OData.Feed("https://d365_instance.api.crm.dynamics.com/api/data/v8.2") to OData.Feed("https://d365_instance.api.crm.dynamics.com/api/data/v8.2", null, [Implementation="2.0"])
Microsoft Dynamics Blog 