[Sarah]

You are right about the “OR” being the problem. When I change it to “AND” it works fine.
The lists are setup with _vLookupID / vLookupParentID fields as per the example.
What I might try is to use powershell to fill in RelatedWorkorderID for every item in the case list so that I can remove the Related_x0200_Case lookup from the query (as it is only for older items – not used in new items).

[Sarah]

Hmm still same issue 🙁

[Sarah]

Ok – its the same screenshot when its over 5000 items (just tested). Please advise. Thanks

[Sarah]

Yes the query has a “or” in it :/
I have temporarily fixed it by deleting some old test items from that list and it is working again (of course) – but it is critical to the business hence i had to fix it temporary so they can use it for now. I have attached the “&vLookupDebug=1” output anyways tho – and will do again after work when I can add some items to make it over 5000 again once noone is working on it.

Attachments:

1. 

   vLookupDebug.png
   

[Sarah]

Hi Alex,

The same issue came up just now again. I have already added the columns I use in the vLookup query as indexes to the list but still get the error.
We are still on version 2018-11-10 (DFFS v4.4.3.55) so I’m not sure if we should update to latest etc or if there is another fix?

Cheers,
Sarah

[Sarah]

I have found a work around for this issue. As the child list had a Lookup column to the parent list which exceeded the 5000 item limit mark, I created a new column in the child list as set it as text field. Then in the vLookup settings from the parent i set to prefill the new text field with the parent items id. Then I added the new field equals curentitem:id in the query and now it works again.

[Sarah]

Great! Adding the query field to the indexed columns did the trick.

Thanks Alex!

Cheer,
Sarah

[Sarah]

Hi Alexander,

Thanks for your reply.
Yes please if you don’t mind would be great to get a sample code for your approach.
Thanks

[Author]

Posts