Loading Profile...
Can I use table-data as input for a different Scaffolding field on a different page?
I know how to use table-data on another page. I'm wondering if it's possible to use the results as list-options in a list-data field on another page. If I do something like this with the list-option escaped:
The drop-down doesn't render (but the text shows the desired data). If I don't escape list-option it renders but the values are "{report-info:expanded:user > data:name}".
|| Owner | {list-data:owner|multiple=true}
{report-block}
{expanding-reporter:data:goal-entities|as=user}
{local-reporter:page:children|source=~cwhunt:Tests}
{local-reporter}
{expanding-reporter}
{report-body}
\{list-option}{report-info:expanded:user > data:name}\{list-option}
{report-body}
{report-block}
{list-data} ||
The drop-down doesn't render (but the text shows the desired data). If I don't escape list-option it renders but the values are "{report-info:expanded:user > data:name}".
I’m thankful
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The best answer from the company
-
You're close - it works better if you use injection. Just change your {report-body} to this and you should be good to go:
{report-body:injected=true}{list-option}%expanded:user > data:name%{list-option}{report-body}
The company and 1 other person say
this answers the question
-
Inappropriate?You're close - it works better if you use injection. Just change your {report-body} to this and you should be good to go:
{report-body:injected=true}{list-option}%expanded:user > data:name%{list-option}{report-body}
The company and 1 other person say
this answers the question
1 Comment Add a comment
This answers the question
-
Thanks, David. That worked perfectly. You rock! Is it possible to filter based on a data field? I tried text-filter and collection-filter but can't quite get it to work. Something like:
{text-filter:user:page > data:name|include=".*cwhunt.*"} -
Inappropriate?If you're filtering based on a data field inside the table-data, put the {text-filter} inside the {expanding-reporter} and just use 'data:name' as the key. Eg:
{expanding-reporter:data:goal-entities|as=user}
{local-reporter:page:children|source=~cwhunt:Tests}
{local-reporter}
{text-filter:data:name|include=.*cwhunt.*}
{expanding-reporter}
1 Comment Add a comment
This answers the question
-
Mumtaz! You've done it again, David! You are an exemplar of responsiveness and acumen!
-
Inappropriate?Is there a different way to do this in 3.2.0? The same code I used before not longer works when I upgrade.
-
Inappropriate?Not that I'm aware of. Is it the report or the list box that's not working now?
-
Inappropriate?Not that I'm aware of. Is it the report or the list box that's not working now?
-
Inappropriate?The list box gets its options as a report from another page using expanding-reporter. In 3.2.0 it's simply blank whereas in Reporting Plugin 3.1.0 it renders the list options. The code is:
|| Owner | {list-data:owner|multiple=true}
{report-block}
{expanding-reporter:data:project-entities|as=user}
{local-reporter:page:children|source=all:Projects}
{local-reporter}
{text-filter:data:unit|include=.*lit.*}
{expanding-reporter}
{report-body:injected=true}{list-option}%expanded:user > data:name%{list-option}{report-body}
{report-block}
{list-data} ||
The page it gets data from has:
{table-data:project-entities}
|| Unit/Group || Name ||
| {list-data:unit}{list-option}admin{list-option}{list-option}cm{list-option}{list-option}lit{list-option}{list-option}ps{list-option}{list-option}sc{list-option}{list-option}fac{list-option}{list-data} | {text-data:name} |
{table-data} -
Inappropriate?Hmm. I suspect the problem is probably with the {text-filter}. What happens if you remove it?
-
Inappropriate?I didn't see any difference with or without the {text-filter}. However, I removed all the line breaks and it renders properly. For example:
|| Owner | {list-data:owner|multiple=true}{report-block}{expanding-reporter:data:project-entities|as=user}{local-reporter:page:children|source=all:Projects}{local-reporter}{text-filter:data:unit|include=.*lit.*}{expanding-reporter}{report-body:injected=true}{list-option}%expanded:user > data:name%{list-option}{report-body}{report-block}{list-data} ||
This is a good enough workaround for me. -
Inappropriate?So we're having this issue, dropdowns disappearing with 3.2. The newline solution brings them back but the data doesn't return.
Any advice for getting back the data? We have a backup if the database
I’m anxious
-
Inappropriate?If you lost them because you edited and saved while no options were available, you should be able to recover them by going to page history, scrolling back through the old pages and then reverting to the first one that has the data you need.
EMPLOYEE
