Databases
StackOverflow2013
Postsdbo
POXPages Mobile Controls Not Refreshing Properly
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POXPages Mobile Controls Not Refreshing Properly
    primarykey
    data
    text
    <p>I have created a single-page app, and it seems to be behaving very badly on some page transitions.</p> <p>I have a View of parent docs, and I then click on a document to load it, OK. I have an 'Add Item' button on the parent to compose a new child doc which will be related to the loaded parent by doc id.</p> <p>The problem is, when I load the new child doc in edit mode, the previous page is still displayed behind it on screen. I now have a messy jumble of controls, and things get worse from there. If I click the 'Back' button on the child doc, I get the background page back at the parent doc page, but now the child doc is still loaded in the foreground in edit mode. If I hit back again, it goes to a parent form with no doc loaded.</p> <p>I use the setting resetContent="true" on all pages, and my command to 'Add Item' is:</p> <pre><code>&lt;xe:moveTo targetPage="ItemPage" forceFullRefresh="true" saveDocument="true"&gt;&lt;/xe:moveTo&gt; </code></pre> <p>I have also tried with:</p> <pre><code>&lt;xe:moveTo targetPage="ItemPage" forceFullRefresh="true" saveDocument="false"&gt;&lt;/xe:moveTo&gt; </code></pre> <p>What am I doing wrong? This is Domino 8.5.3FP3 with Upgrade Pack 1.</p> <p>OK, here's the button code in the page heading:</p> <pre><code>&lt;xe:djxmHeading id="ReqHeading" label="Requisition" back="Back" moveTo="viewAllRequisitions"&gt; &lt;xp:this.facets&gt; &lt;xp:button value="Add Item" id="actionFacetButton1" xp:key="actionFacet"&gt; &lt;xp:eventHandler event="onclick" submit="true" refreshMode="complete"&gt; &lt;xp:this.action&gt; &lt;xp:actionGroup&gt; &lt;xp:saveDocument var="document1"&gt;&lt;/xp:saveDocument&gt; &lt;xp:executeScript script="#{javascript:sessionScope.RequisitionID = document1.getDocument().getUniversalID();}"&gt; &lt;/xp:executeScript&gt; &lt;xe:moveTo targetPage="ItemPage" forceFullRefresh="true" saveDocument="true"&gt;&lt;/xe:moveTo&gt; &lt;/xp:actionGroup&gt; &lt;/xp:this.action&gt; &lt;/xp:eventHandler&gt; &lt;/xp:button&gt; &lt;/xp:this.facets&gt; &lt;/xe:djxmHeading&gt; </code></pre> <p>and here's the new child doc page:</p> <pre><code>&lt;xe:djxmHeading id="ItemHeading" label="Add Item" back="Back" moveTo="RequisitionPage"&gt; &lt;/xe:djxmHeading&gt; &lt;xp:this.data&gt; &lt;xp:dominoDocument var="document1" formName="Item"&gt; &lt;/xp:dominoDocument&gt; &lt;/xp:this.data&gt; &lt;xp:label value="Job Number:" id="labelSubject1"&gt;&lt;/xp:label&gt; &lt;xp:inputText id="txtSubject" value="#{document1.JobNumber}"&gt; &lt;/xp:inputText&gt; &lt;xp:br /&gt; &lt;xp:label value="Item Description: " id="lblDescription"&gt;&lt;/xp:label&gt; &lt;xp:inputText id="txtDescription" value="#{document1.Description}"&gt;&lt;/xp:inputText&gt; &lt;xp:br /&gt; &lt;xp:label value="Quantity: " id="lblQuantity"&gt;&lt;/xp:label&gt; &lt;xp:inputText id="txtQuantity" value="#{document1.Quantity}" defaultValue="1" maxlength="3" size="3"&gt;&lt;/xp:inputText&gt; &lt;xe:tabBar barType="segmentedControl" id="tabBar1"&gt; &lt;xe:tabBarButton id="tabBarButton1" label="Submit"&gt; &lt;xp:eventHandler event="onClick" submit="true" refreshMode="complete"&gt; &lt;xe:this.action&gt; &lt;xp:saveDocument var="document1"&gt;&lt;/xp:saveDocument&gt; &lt;/xe:this.action&gt; &lt;/xp:eventHandler&gt; &lt;/xe:tabBarButton&gt; &lt;xe:tabBarButton id="tabBarButtonEdit" label="Edit" rendered="#{javascript:!document1.isEditable()}"&gt; &lt;xp:eventHandler event="onClick" submit="true" refreshMode="complete"&gt; &lt;xp:this.action&gt; &lt;xp:changeDocumentMode mode="edit" var="document1"&gt; &lt;/xp:changeDocumentMode&gt; &lt;/xp:this.action&gt; &lt;/xp:eventHandler&gt; &lt;/xe:tabBarButton&gt; &lt;/xe:tabBar&gt; </code></pre> <p>OK, I have given up on the single-page app for now as I find it does not refresh properly on creating any new docs. This seems to be broken as far as I can tell.</p> <p>I am now trying to use multiple pages, but when I use a new xpage for the moveTo target, I get an error "destination view not found: null. Is this supposed to work?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJohn
    1. USJohn
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COThe syntax of your `moveTo` action looks correct, but outside of the context of the surrounding components, it's impossible to be certain. Post as much of the source code as you can without violating any disclosure agreements.
      singulars
      1. POXPages Mobile Controls Not Refreshing Properly
      1. USTim Tripcony
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload