I can't understand why would JSON be any good as a parameter option here.
However, just looking at the SQL fields and values do differ (don't know the table's structure, but guessing based on what I see).
DrugDetails vs. two fields/values in JSON.
@Scott Roth example shows what's an approach (not only though).
So, a bit more information would be helpful.
Thanks to everybody for your inputs.
Thank you very much, Nigel.
I know for aux... but it turned out that I was making mistake when trying to implement this, however simple that is.
Thanks Cristiano,
I know that, but I need that not from BPL but from some custom code as mentioned.
Thanks!
It works it seems.
Isn't it:
"Mapped the table in the Global Mappings for %ALL"
.png)
Thanks both Robert and Rich. I tried %ALL already and mapping, but it did not work...
I am missing something, obviously.
Here's what I have done:
- Created %ALL namespace
- Created a table OriginalNamespace.TableName
- Mapped the table in the Global Mappings for %ALL I used the Portal's System > SQL to create the table and to insert/select data from it.
As mentioned, not visible unless in the original namespace.
Managed to get it in the list. Closing this (for now).
It is giving a result for either top n or without it, but only when "group by" is not there.
As soon as I add that line it spits out the error.