You are viewing limited content. For full access, please sign in.

Question

Question

Metadata - Dynamic Fields - DirectSQL

asked on September 18

Morning!

I'm experimenting with the new "Data Query as a source for Metadata" drop-downs options.

Seem to be hitting a strange roadblock, wherein I cannot pick any field other than the field I am in as a parameter for the data query.  Of course, when you select that field (just to sense-check the logic) it is flagged up as an error.

I have tried doing this from scratch, checking that the field types match, tried the Data Query on both fields (whichever field you have selected for the Dynamic Rule application appears as the only option for the parameter).

Hoping this is a bug fix and not hardcore ineptitude on my part!

Screenshots above.

param_surnames is a Text field and not involved in any other operations (literally a new field)

dropdown_picklist is a dropdown that is meant to be populated with the query results

Really fun behaviour I have also noted...if you delete the Rule without finishing it off then the dropdown immediately turns into a list of radio buttons!

Any ideas?  

Thanks,

Justin

0 0

Answer

SELECTED ANSWER
replied on September 22

Justin,

Currently, a dynamic field can only accept input parameters from other dynamic fields, which means if you are chaining them together, the first rule in the chain needs to be a lookup with no input parameters.  Our next update in October will remedy this, along with letting you map multiple rule output parameters to multiple fields (think a single address lookup rule to multiple form fields).  Thank you for the feedback and hopefully you'll be all set in about a week or so.

Andrew

0 0

Replies

replied on October 1

Just as a follow-up, I have now tested this and confirmed (to myself + client) that the behaviour is as you stated, Andrew. 

Thanks again.

1 0
replied on September 18

That is a current limitation of the user interface. Updates to it to allow reuse of the same query in multiple fields is currently scheduled for next month. 

0 0
replied on September 22

Hi Miruna,

Thanks for the quick reply - the issue for me is that I cannot supply a parameter at all at the moment.

Are we only supposed to use queries with no parameters, at the moment, to use the functionality?

Many thanks,

Justin 

0 0
SELECTED ANSWER
replied on September 22

Justin,

Currently, a dynamic field can only accept input parameters from other dynamic fields, which means if you are chaining them together, the first rule in the chain needs to be a lookup with no input parameters.  Our next update in October will remedy this, along with letting you map multiple rule output parameters to multiple fields (think a single address lookup rule to multiple form fields).  Thank you for the feedback and hopefully you'll be all set in about a week or so.

Andrew

0 0
replied on October 1

Hi Andrew,

Thank you for your detailed reply - that's great to hear this is getting addressed in the October release!

Best wishes,

Justin

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.