Has anyone successfully injected data into the URL of the website widget? The URL help specifically shows using the curly bracket syntax to reference views, but when the widget actually loads, it simply puts {View.Field} into the URL.
Ok well now I have to try it.
Ooo, I just saw this on another post somewhere. Hold.
(I think you had to put single or double quotes around the {} field)
Panel card grid column linking - Kinetic 202X - Epicor User Help Forum (epiusers.help)
Oh–yours is a different widget. @klincecum you’re up. I gotta go!
It worked for me.
I had https://test.com/fff?{KEV_Get_Assemblies_0_0.Calculated_AssemblyName}
It went to https://test.com/fff?Accord.Math.Core
Huh. On 2023.1.5?
2023.1 naked.
This is a cloud environment, but a test one that is behind. I can upgrade tonight and see
if there is a regression. (As soon as I can get @josecgomez out of it lol)
Out of curiosity, did you type your view.column correctly? I believe a typo might just print it out like yours is.
Also, if you are creating your view later on, you may have to click reload on the widget,
because the view does not exist when the widget tries to load.
In this case, the full placeholder I’m using is {ReportParam.Jobs} on the Job Traveler print app. The autocomplete helpfully suggests it in this case.
Does the web widget reactively update the URL when placeholder values change? I also tried using property-set on the ‘url’ property of the widget, but this doesn’t seem to work.
[edit]This was in Chrome. Just tested in Kinetic client with same result.
In this case upon first load,
ReportParam.Jobs would be empty, but I would assume that the web widget would reactively update the URL once a job is filtered. No?[/edit]
That has been my experience.
1 Like
Also, clicking reload on the widget has no effect on the URL.
Go ahead and add a textbox field to that screen and bind it to ReportParam.Jobs
See if that updates as expected.
Hey! I was watching that!
I’m sensing a pattern here.
Doh! I keep screwing up my redaction. Safety first! 
Well What the …
I’m not sure why it’s not working.
Just for giggles, try marking it as a key field on the widget.