Home › Forums › QuickApps Forum › The following error occurred: IEntity could not be found using criteria 'Entity Namespace = UATACT, Name = ACTClientAssociate'.
- This topic is empty.
- AuthorPosts
-
- 03/05/2012 at 1:50 am #5070
AnonymousParticipantthis seems to be an issue within our site config/programming. please ignore
- 03/06/2012 at 9:04 am #6307
AnonymousParticipantBCS is now working correctly, but still getting this error from the qlistform web part. any advice is much appreciated!
- 03/06/2012 at 10:06 am #6308
AnonymousParticipantHi Carrie,
What's the error you get now?
- 03/06/2012 at 10:09 am #6309
AnonymousParticipantThe same.see attached.
- 03/06/2012 at 10:15 am #6310
AnonymousParticipantDo you have a CAML filter in set up or some search criterias?
What's your QWP version?
Please add more details about your web part configuration.
Thanks,
- 03/06/2012 at 10:24 am #6311
AnonymousParticipantSee attached. The issue only arises on the qListform wp when trying to view or edit properties. No CAML.
- 03/06/2012 at 10:41 am #6312
AnonymousParticipantFrom your screenshots I can't see any field or reference to the error message (UATACT or ACTClientAssociate). What's the name of the list/lists you want to display?
I'd suggest you to try to isolate the problem.
Use the web part to display a different list with the minimum fields possible, if that succeeds then move to the list that fails, do the same here, remove any configuration (save it to a text file) and display one field only.
If it still fails, create a new page and add a qListView on it and replicate the minimal configuration here.
- 03/09/2012 at 9:27 am #6313
AnonymousParticipantWe have resolved this. the issue was that we populated the external lists in one environment, then moved the list to another. The BCS model between the two environments was slightly different (namespace, db name) and this caused the error. solution is to populate the external lists AFTER changing environments.
- 03/09/2012 at 9:38 am #6314
AnonymousParticipantI'm glad to hear that.
- 03/12/2012 at 7:04 am #4172
AnonymousParticipantupon move to PROD, qlistform web part is now throwing this error. i don’t see the namespace referenced anywhere in the web part configuration…..where would this call be coming from?
- 03/12/2012 at 7:04 am #6315
AnonymousParticipantHi Carrie,
Would you mind to mark your question as answered so other people can benefit?
Thanks,
-
- AuthorPosts
You must be logged in to reply to this topic.