— The Forums are now read-only —
— All new activity now takes place here: —
Good Afternoon,
Hoping someone has an answer for this. I'm hoping its not unsupported. I'm trying to write a fairly complex report. In fact, I currently have a parameter embeded in the join expression. It works quite nicely, however, I need to bring the data to Excel through an ODATA connection and this is where trouble ensues. I understand that I ODATA handles everything through the URL. The report requested, the filters, etc. Is there a way to get the ODATA url to recognize and assign a parameter?
let
Source = OData.Feed("https://Thelostreport.com/odata/CompanyTarget/Single Table Test 3?$filter=targetUser eq 1646")
in
Source
Hi -- does this post give you what you want?
Unfortunately no. In that post, he never creates a parameter within the general inquiry. I created a parameter in the General inquiry itself, I then need to somehow feed it a value through an ODATA URL. The reason I need to feed it a parameter is because the join expression depends on it. What I have started doing to get around it is creating multiple odata result sets that I feed into excel and do the joins on that level. If I did not have the parameter in the join expression, I could forgo general inquiry parameters and just use the Odata filter.
Reading from the top, I was thinking, "what's the difference between OData filtering and using a parameter to do the filtering", but then you stated it again and I finally got it. You're using the parameter in the JOIN.
Unfortunately, as far as I know, it's not possible to pass a parameter through OData. But if anyone knows a way, I would love to know what it is.
By using this website, you agree to our Terms of Use (click here)
