I am using rbf_setViewSelector("integrationName", value) for a lookup field and upon clicking the selector button, the view does get filtered. However, when I type in the actual input field itself (instead of opening the lookup selector window), there doesn't seem to be any filtering applied. Looks like a bug to me. Could somebody please confirm this to me?
Are you trying to use the rbf_setViewSelector on dependent lookups or External Objects?
Just normal lookup selector field.
Any luck with finding out whether this is a known issue or not please?
Yes. That is a bug. Thanks for catching it.
We will fix it and let you know the update.
TP id #32223
Thanks and Regards,
Any dates on when this would be fixed please?
This is planned for v220.127.116.11 release which is due in the month of March 2016.
This has been addressed in the forthcoming 4.2 release.
This has not been fixed in V4.2. beta release. The inline-autocomplete still shows all the results regardless of what ViewSelector you have applied on the Lookup field.
Iram, this may have been missed in EAP Update 4. However, can confirm that the fix has been committed to release branch.
Can you also please try Ctrl + F5 to refresh browser cache.
Just discovered that its the original ID that is not working for the rbf_setViewSelector() function where as it is working with the normal ID for the view. The original ID issue needs to be looked at for this function.
As per documentation documentation.progress.com/.../, it requires ID only not Original ID.
Ok thanks for that. However does that mean we have to keep changing the ID every time we upgrade?
No. ID won't change after upgrade.
I exported the app from my current version 4.0.4. and reimported it in 4.2 beta version and the view ID has changed. Any reasons why?
Any updates on this issue please?