Skip to main content
Solved

Attribute value to WHERE Clause in workspace runner not working


Hi,

I am attempting to feed an attribute value into a published parameter WHERE Clause in a WorkspaceRunner (the workbench reads an AGOL feature service, which i want to limit the number of features it has to read as its very slow).

FeatureReader is not an option as I need to read attachments.

In the error log it shows that instead of using the attribute value @Value(SQL), it is the actual text @Value(SQL) that is getting used. Am I doing something wrong? Or is this a bug?

Thanks

Best answer by takashi

Hi @n543, I was able to reproduce the same error, if I have created the published parameter from the WHERE Clause parameter in the AGOL reader. I think it's a defect. Hope someone from Safe would take a closer look at this. > @NatalieAtSafe

In the interim, it might be a workaround if you create a new published parameter with Text or Text (Multiline) type and link the WHERE Clause parameter to that.

View original
Did this help you find an answer to your question?

5 replies

takashi
Contributor
Forum|alt.badge.img+19
  • Contributor
  • April 6, 2018
Could you please paste the actual error log or its screenshot here?

 

 


  • Author
  • April 6, 2018
takashi wrote:
Could you please paste the actual error log or its screenshot here?

 

 

Yes of course:

 

 


Forum|alt.badge.img
  • April 6, 2018

I had a similar issue when trying to pass the list of attribute to compare for a Matcher in the child workspace as the value of and attribute from the calling workspace. I worked around that by using a SystemCaller calling fme.exe with the required parameter values.


takashi
Contributor
Forum|alt.badge.img+19
  • Contributor
  • Best Answer
  • April 6, 2018

Hi @n543, I was able to reproduce the same error, if I have created the published parameter from the WHERE Clause parameter in the AGOL reader. I think it's a defect. Hope someone from Safe would take a closer look at this. > @NatalieAtSafe

In the interim, it might be a workaround if you create a new published parameter with Text or Text (Multiline) type and link the WHERE Clause parameter to that.


  • Author
  • April 6, 2018
takashi wrote:

Hi @n543, I was able to reproduce the same error, if I have created the published parameter from the WHERE Clause parameter in the AGOL reader. I think it's a defect. Hope someone from Safe would take a closer look at this. > @NatalieAtSafe

In the interim, it might be a workaround if you create a new published parameter with Text or Text (Multiline) type and link the WHERE Clause parameter to that.

Thank you! The workaround works for me, so I will use that methodology for now.

 

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings