Forum Discussion
Hi Jayraj,
thank´s a lot! This was indeed helpful!
I have a talent for fixing complex Aras problems, but you wouldn´t believe how often I forget basic and “primitive solutions”
- ‘Auto Search’ -> Yes, of course disabled
- ‘Default Search’ –> Thanks for the tip!!! I never have used it in all the years and never have noticed that this option exists at all
- onBeforeGet -> Of course! Completely forget about this option, even I have done it before
I use an onGet for the federation. But of course I can an onBeforeGet BEFORE querying for federated data at all.
This way I can check all kind of user settings like ‘maxResults’,’pageSize’ and their filter values. And it has the advantage that I can give direct user feedback (error message) if their search settings doesn´t match the requirements.
I didn´t like my idea with the custom search mode, cause it would influence all other ItemTypes as well.
@Edit: I wrote the text above before actual testing the solution. I think the above ideas work fine regular ItemTypes.
But in my current federated ItemType it turned out that we cannot use "onBeforeGet" when using an "onGet" Method. The "onBeforeGet" simply is not triggered.
I right now try to figure out how to add more restrictions to the "onGet" Method. Unfortunately this event type is a bit special. Well, I will of course give it a try!
Hello Angela,
Are you using a federated Item Type? And are you looking for all these restrictions on Search of a federated Item Type?
- AngelaIp4 years agoIdeator I
Hi Jayrajvh,
yes, it´s a federated ItemType!
I have my Innovator database and in parallel a second database that contains millions of measurement values from production testing. I want to provide a way to analyze the measurement values inside Innovator.
I use an onGet Method to connect to the second database, read the data and display them in a standard grid.
The standard item grid is not the best choice to work with data, but in the beginning it´s a simple way to have some kind of access to the data at all. I think I will later move to reporting options, so users don´t have general access to the data.So far I just use a simple restriction in the SQL query ("Select TOP(500)").
I haven´t tested all of your ideas yet. Your idea regarding using a "flag" as indicator sounds promising! I just still need some time to think it through. I maybe can provide a code sample later.