Parameterized saved searches
Currently, we are able to create parameterized functions by using the 'let' command.
Example:
let f=(a:int, b:string) { strcat(b, ":", a) }
This sounds great in concept... until you find out that this only works if you type your entire function at the beginning of each query because these functions aren't 'stored' and you can't save the function as a saved search because then the search engine starts complaining when there is no output...
So, saved searches behave right now as SQL views. Even though there is a "function" concept it doesn't seem like we can create parameterized functions at this time.
Having this feature would be extremely helpful to those of us who are pumping custom data into OMS and are trying to fetch these records segregating the data into different categories by tenant and so on.
Arturo Vazquez
shared this idea
Thanks for your feedback. Adding parameters to saved functions is definitely something we would consider for the future.
5 comments
-
Mark Allen
commented
As we seek to build out a robust library of queries, the inability to use parameterized shared functions causes serious maintainability issues for us. This manifests as copy-paste in many of our shared queries, and if that function logic needs to change, significant updates to many queries.
-
Tony Curtis
commented
This would be very useful!
-
Bryan Allen
commented
Agree. It's a highly needed feature that would be extremely helpful.
-
Indrajeet Valera
commented
Reuse of parameterized scalar & tabular functions will be great value add.
-
Dmitriy Beryoza
commented
Ability to save functions and use them from multiple queries would be great for code management and reuse. Any update from ALA product management on plans for this functionality?
Thanks!