Skip to main content

XrmToolBox: AutoNumberUpdater - new StateCode filter

Post a Comment

CRM 2013: Condition for attribute 'template.templatetypecode': null is not a valid value for an attribute. Use 'Null' or 'NotNull' conditions instead.

Lately I was fighting with an issue that on some CRM instances the default email templates view in the Templates section of CRM 2013 did not show up and only showed me this error message:

Condition for attribute 'template.templatetypecode': null is not a valid value for an attribute. Use 'Null' or 'NotNull' conditions instead.

After searching for a long time I found the simple bug. Throught migration from 4.0 to CRM 2013 over CRM 2011 and changing customizations it seemed that CRM got messed up or was not able to handle the changes very well.

The issue here was to go to the views section of the Email Templates entity and to make sure there is only ONE default public view. If there are two you will get strange system behavior.

I fixed this problem through updating the isdefault property of the second unwanted default view in the SavedQueryBase data table. The id of this view  you can retrieve by openen the view and by copying it out from the URL.

Én voilá the problem was solved and the view worked again.
Labels:

Comments

  1. Neha VaidJanuary 23, 2018 at 2:42 PM

    I am getting the same error on the Product Form when adding the value to Price List Field.
    what can be the reason for this?

    Condition for attribute 'productpricelevel.productid': null is not a valid value for an attribute. Use 'Null' or 'NotNull' conditions instead.

    ReplyDelete

Post a Comment

Popular posts from this blog

Yet Another Address Autocomplete PCF Control–powered by Bing

In this blog post I will not go into detail in how to install all the pre-requisites that are required to build and run PCF controls. My goal was to build a new PCF control and get into coding of PCF controls as fast as possible. Here are a few links to articles that will help you installing the pre-requisites (Microsoft PowerApps CLI)  https://docs.microsoft.com/en-us/powerapps/developer/component-framework/get-powerapps-cli Other good references to get into this topic: https://toddbaginski.com/blog/how-to-create-a-powerapps-pcf-control/ https://docs.microsoft.com/en-us/powerapps/developer/component-framework/create-custom-controls-using-pcf I looked through the Guido Preite’s https://pcf.gallery/ which will help you find appropriate use cases / examples for your own needs. It did not take very long to find a simple example to start with: Andrew Butenko's https://pcf.gallery/address-autocomplete/ A few moments later I had the idea to create yet another address autocomplete...
16 comments
Read more

Regarding SPFieldMultiLineText (Add HTML/URL content to a field) programmatically

I recently tried so set some HTML content in a SharePoint list column of type SPFieldMultiLineText. My first approach was this piece of code: SPFieldMultiLineText field = item.Fields.GetFieldByInternalName( "Associated Documents" ) as SPFieldMultiLineText; StringBuilder docList = new StringBuilder(); docList.Append( " " ); foreach (DataRow docRow in addDocs) { DataRow[] parent = dr.Table.DataSet.Tables[0].Select( "DOK_ID=" + docRow[ "DOK_MGD_ID" ].ToString()); if (parent != null && parent.Length > 0) { docList.AppendFormat( " {1} " , parent[0][ "FilePath" ].ToString(), parent[0][ "Title" ].ToString()); } } if (docList.Length > 0) { // remove trailing tag docList.Remove(docList.Length-5, 5); } docList.Append( " " ); string newValue = docList.ToString(); item[field.Title] = newValue; What this code does is to get all associated documents to the main document and to add these docu...
1 comment
Read more

CRM 2016 SP1: Solution import failed with Solution With Id = 12ac16ec-41d5-1685-a230-0b1c31499250 Does Not Exist

Importing Solutions with the upgrade solution (holding solution) option is still not stable with CRM 2016 SP1 On-Premise. Ronald Lemmon already posted the same issue on his blog: http://ronaldlemmen.blogspot.de/2015/11/solution-with-id-86ac16ec-41d7-4685.html I expected it to be fixed with SP1 but it is still happening every now and then. With this query and the solution id (guid) of the error message you are able to find records in the ProcessTriggerBase table that reference the guid of a failed import from a holding solution that is not existing in the system anymore. select * from ProcessTriggerBase where solutionid = 'YOUR_SOLUTION_GUID' Due to this reference to a solution id not existing in the system you will not be able to import a new version of the target solution to be updated. What I did and this is probably not a supported solution is to update the guid to the actual target solution that is currently deployed in the system. To find out the id of ...
3 comments
Read more