Hi Angela,
Thanks for quick answer. As you mentioned I was hoping on some secret way of achieve this :D
Anyway I have an itemtype with onGet method implemented which call SQL stored procedure (to accept parameters for filtration) and it works.
But... to cover all possible combination of filtration (like, not like, equal...) and all type of properties (string, date, list...) for every column takes a lot of work and nerves.
I'm looking for more elegant way... with more configuration and less coding...
Maybe Aras only need to implement some mapping logic between poly source properties (maybe also some conversion logic...) and poly itemtype would be way more useful.
Hi Jan,
I agree, somekind of mapping logic would be the best solution. Even if you merge two or more ItemTypes inside an onBefore/AfterGet Method, it´s still would require a lot of coding.
Do you use a custom onGet Method or the Aras Federation sample?
I remember I still have this open post in this forum:
I use both version (custom and Aras) in parallel and both have their pros and cons. The Aras Federation sample contains a mapping ItemType so it´s faster to implement and doesn´t require custom code. But query speed is higher with the custom variant.
