Support Forum

Unfortunately our documentation is very lacking here - but we are working on it:

You go to your SubPage and create a new Page Source as a "new, empty XML". You add there a root element and child attributes or elements which you want to display. Then, in your Go to Subpage action, you map the current row to the root element in the Sub Page.

This concept allows you to use the same Sub Page for editing of different trees from the parent page, even those where elements and attributes are different to those from Sub Page.

In future we also might be able to do it easier without a requirement for an own Sub Page tree, if your Sub Page was not meant for reuse, but currently this is the way to go.

Hi Jan!

Without knowing your sample - are you sure you need a mapping at all?

In case you just want to show a distinct row of your table, you can also do the following:
Reuse the same Page source on toppage and subpage (the tree is really shared as long as you don’t use the option “Load Data|On Every page”, so no new loading of all records is done when entering the subpage)
When clicking the button, label or whatever control enters the subpage, save your unique row-key in a second tree before.
You can do this by using an “Update Node” action like:

In the subpage, you can select the wanted row by using that @edit-id as constraint.
E.g. you can define a repeatable table with following “Create for each item in” XPath setting:

Or if you don’t want to create a table but just a Label, you can set its text by using a similar XPath

If you do not only want to show but also edit your row data, you can also copy the row to a different tree (using an “Append Node(s)” action) and modify that one.
In the subpage, the second tree is modified. If editing should be cancelled, you simply throw it away; in case of saving, you can write back the data to the original row after closing the subpage.

Hope this helps.

---

Altova MobileTogether Experts