In IEC code when using LoadCollectionRequest, is there a way to bypass or disable any default filters configured on the IDO?
The only place I thought you could put a permanent filter on an IDO was inside a Form. (I could be wrong).
I don't know if it overrides it or not but the LoadCollectionRequestData class has a Filter parameter. You could try .Filter = "";
In the IDOs form there is a Filter tab and button. This allows you to set filters for either the entire site, groups or individual users. We use it to do automatic filtering on company code. But we've run into a few instances where it would be better to control all filtering with the IDO.
Also, setting Filter="" on the LCR does not bypass any IDO filtering, unfortunately.
Learned two things today
This might be a janky solution, but could work. What if you extended the IDO and removed the filter there? You could keep the main IDO with the filter and then use this "secondary" one unfiltered.
We've done something along that line but in general, as a vendor developer, I try to avoid using extensions as part of our core product. But... that's not a bad suggestion either.
What you could do is use the IDO Export wizard to export the IDO as XML, find and replace the IDO name with a new name and remove the AccessAs (ServerName). Import that new IDO definition, check the IDO out, remove the filter, run your code against THAT IDO. Not perfect, but may work like you need. Only issue is any patches that update the original IDO would have no impact on your hijacked IDO
That is essentially what we did for a few IDOs in order to get around the immediate problem. I don't like it. Its a poor solution and yes, creates massive maintenance overhead. Hence why I am trying to find an answer to my question.
have you tried to implement an extension class for the IDO and implement your custom load collection override? i haven't tried it, but curious whether framework would still apply IDO filters on-top
