« New CRM SDK 4.05 - Check out the readme! | Main | Replacing Built-in Entities / Offline Client »

Query Builder Error after Import

I had fun today tracking down a error that I created by importing an entity that had a lookup field on a form that was from another entity that the target system didn't have.  The result was after publish of the imported entity I could no longer bring up the entity form without getting a simple page that said "Query Builder error".

Using a platform trace I was able to figure out the name of the field having the problem.  Since it was from a lookup the field missing was something like ctc_myfieldID  which was the Id for the lookup field to be stored in.  On a suggestion from Mark Harrington from the CRM team, I added a dummy attribute with the same name.  Once that was done, I was able to publish the form without the lookup and then I was able to finally remove my dummy attribute.

The other obvious way you can fix this problem is to import the missing entity - but in some cases like this one I didn't want the missing entity in the target system.

And for those of you that happened to notice that my blog posts slowed down in May - that didn't mean I wasn't busy working but I've been working on trying to wrap up a project that I started about a year ago and it involves close to 600 pages.  Stay tuned to this space for an announcement with tons of more details on my mystery project!

Posted on Tuesday, June 10, 2008 at 04:29AM by Registered CommenterDavid Yack | Comments2 Comments

EmailEmail Article to Friend

Reader Comments (2)

I have had the problem several times, and fixed it the same way. The problem comes with an odd behavior. When an attribute is missing on an entity, the entity icon in the sitemap and on the icon on the new button is missing.
June 11, 2008 | Unregistered CommenterHenrik Ditlevsen
How do you do a platform trace? I have this same issue.
July 29, 2008 | Unregistered CommenterPhilip Massey

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
All HTML will be escaped. Hyperlinks will be created for URLs automatically.