From: Yaron K. <ya...@wi...> - 2011-07-08 20:34:57
|
Hi, Okay, that makes sense - but unfortunately, I don't think there's any way to do this currently in SF. -Yaron On Fri, Jul 8, 2011 at 1:31 PM, Justin Preece < pr...@sc...> wrote: > ** > Thanks for the reply, Yaron. > > At it's simplest, I would like to know how to reference the value of an > iterated form field within the form edit page. Then I can use it in queries, > expressions, etc. on that form. > > For the purposes of discussion, let's just say that I want to restrict the > editing of certain iterated form fields on the basis of their value: > > {{{for template|My Repeater|multiple}}} > > {{#ifexpr: <Current value of Field 1> = <Some Number> > | Field 1: {{{field|Field 1|restricted}}} > > | Field 1: {{{field|Field 1}}} > }} > > {{{end template}}} > > > This is possible in a non-iterated form... > > {{{for template|My Non-Repeated Template}}} > > {{#ifexpr: {{#show: {{PAGENAME}} | ?Field 1 }} = <Some Number> > | Field 1: {{{field|Field 1|restricted}}} > > | Field 1: {{{field|Field 1}}} > }} > > {{{end template}}} > > > ...I just can't figure out how to do it inside of a multi-instance > template. > > - Justin > > > On 07/07/2011 08:31 PM, Yaron Koren wrote: > > Hi Justin, > > Yeah, I don't believe such a thing is possible - I don't think you can > connect internal objects to their corresponding template instances. > > What is it specifically that you want to modify in the editing? Maybe > it's already possible with "show on select". > > -Yaron > > On Thu, Jul 7, 2011 at 6:30 PM, Justin Preece < > pr...@sc...> wrote: > >> I am trying to access the values contained within multi-instance form >> fields on the _form edit_ page using an inline query, to no avail. >> Reason: I'm trying to use field data to conditionally restrict the >> editing of certain fields in a repeater on a row-by-row basis. >> >> {{#show: {{PAGENAME}} | ?my_prop }} works fine on any field the parent >> form, but not on an iterated list of fields contained within a >> multi-instance template, even if I try to reference an SIO tied directly >> to each iteration. For example (on a form): >> >> {{{for template|Parent Form}}} >> >> {{{field|Some Form Property}}} >> >> {{#show: {{PAGENAME}} | ?Some Form Property }} <!-- works --> >> >> {{{end template}}} >> >> <!----------------------------------------------------> >> >> {{{for template|My Repeater|multiple}}} >> >> '''Field 1:''' {{{field|Field 1}}} <!-- delivers the correct, >> iterated value...but as an input field --> >> >> {{#show: {{PAGENAME}} | ?Field 1 }} <!-- doesn't work b/c >> PAGENAME refers to parent form --> >> >> {{#ask: [[My Current SIO::{{PAGENAME}} ]] | ?Field 1 }} <!-- >> doesn't work either; returns Field 1 for /all/ SIO's on this page --> >> >> {{{end template}}} >> >> >> How can I access iterated field data with parser hooks and queries? Any >> ideas? >> >> Thanks, >> Justin Preece >> ** >> ** >> >> ------------------------------------------------------------------------------ >> All of the data generated in your IT infrastructure is seriously valuable. >> Why? It contains a definitive record of application performance, security >> threats, fraudulent activity, and more. Splunk takes this data and makes >> sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-d2d-c2 >> _______________________________________________ >> Semediawiki-user mailing list >> Sem...@li... >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >> > > > > -- > WikiWorks · MediaWiki Consulting · http://wikiworks.com > > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com |