I am a new user to LiveCycle (LiveCycle ES4 to be exact) and am having an issue with my second Master Page. I only want the second Mast Page to appear if the content from Page 1 overflows onto Page 2. I have tried changing the "Presence" on the second MasterPage to Hidden but the program won't allow me to choose any option other than Visible.
I have tried Google and Adobe and both have basic information regarding Master Pages but nothing specific enough to help me in this situation. Actually, I haven't been able to find a source with any real helpful information regarding LiveCycle.
On the main page that represents your flowed page, in the Object properties tab, if you select the Pagination tab, you can set overflow properties of this page to use your second master page (ensure it is named so you can reference it). If your first page never overflows, then you should never see the other master page.
Related
I've got an issue due to a timing issue with react-admin, that i'm looking for a little help on.
The situation is where user A creates a resource, and user B, on a different PC, then goes to list and edit that resource.
For user B, the list page loads the full dataset of 10 resources, then the edit page re-loads the single resource that is being edited.
However, the specific process on the edit page seems to be:
Render page
Render resource cached from the list page
Request the single resource from the API
Populate the edit form with the updated values from the API
Set the form to dirty
That last point is critical, since I have an action button that is only enabled if the form is pristine, so the user has to save any changes before triggering the action.
But in this case, the list view and the edit view seem to return the same data for the resource, so I'm not sure why the form is being set to dirty.
Any thoughts?
Regards,
Andy
This isn't a complete answer, but I hope it helps you save some time. I recently upgraded React Admin version from 3.5.3 to 3.6.0. I noticed that the Save button is now sometimes disabled unexpectedly, and inconsistently. For example, I may navigate to the edit view of a resource by clicking a link and the Save button is enabled, but if I refresh the page, the Save button is disabled. Apparently, the Save button is supposed to be disabled when the form is pristine. So between 3.5.3 and 3.6.0, it seems that some changes were made to either the pristine handling or the Save button's reaction to pristine, and it is not working consistently.
I see there is a new issue opened three days ago regarding overriding the Save button behavior, wrt pristine. https://github.com/marmelab/react-admin/issues/4913 . So, it seems the dust hasn't settled on this behavior. Perhaps a bug will be found.
In experience editor, whenever clicking on "Add here" button, getting duplicate entries of renderings.
Below is the image for reference. I am using Sitecore 8.2
Use Rendering id's to see if the both are same or different. Add the two renderings to the item in two different placeholders and then check the raw values in the presentation details of the item.
1.If both are same, Then it is caching issue. just clear the cache.
2.If both are different, then there is rendering available with the same name. If it is a duplicate then copy the rendering id from the presentation details and search it in the sitecore content tree and once you have a hit. delete it.
I am using Adobe LiveCycle Designer ES 8.2 to create a PDF for a survey. I've managed to create the form from scratch using Flowed content boxes to allow the fields to dynamically expand so that I can print out the survey later.
The issue I am having right now though is that if a field is expanded and it pushes other fields below it beyond the page range, it will create a new page consisting of what couldn't fit on the previous page. This is fine, but I would also like the form to automatically move the content below the last page up. Basically, anytime a page is moved into a new page there is a lot of white space and id like the next page to be moved up under the newly positioned fields.
Thank you
You will need to configure the pagination of your Subforms using the Object > Pagination palette. You can also use the Keep With Next/Previous option to control the grouping of the objects on page break. Also make sure that your top level subform is set to Flowed.
I have a report with a page break in it that I want to remove, but I don't know where the break is being added. It could be on a table, a group, or I don't know where else.
I checked the tablix properties and group properties for each portion of the report to see if "add a page break before" or "add a page break after" were checked, but didn't find anything.
Is there something i can search for in the RDL source code that will help?
I usually find this occurs when the item (tablix, chart etc) will fit entirely on a new page but not entirely on the page where the control starts. For example if you have a header on page 1 but not on page 2 or you have a chart before your tablix and the tablix will not fit entirely on Page 1 but will fit entirely on Page 2 it chooses to put the tablix on Page 2 instead of half on Page 1 and half on Page 2.
If this is your issue try placing all elements inside another element (such as a rectangle, list or another tablix).
We would need more information to give a more specific answer. Can you post screens of the pages either side of the elusive page break?
I was exporting to report type Web Archive (MHTML) and the page break was coming from the interactive height of the report. Once I set it to zero I no longer got the page breaks.
In one of my custom application user wants to keep EditForm.aspx open once list item is created and he can keep saving the same record without redirecting user to DisplayForm.aspx page.So what I'm doing after list item creation I'm loading EditForm.aspx again.
Now the problem is when form is opened in Edit mode and if existing field is modified that doesn't gets updated in the list item but if something new added to the field then it gets saved to the list. I believe it's postback issue but not sure how to pass latest form data upon save.
If this was my task, I would create a new application page that replaces the edit page on that list.
(You can use powershell / object model to set the url of the new / edit / display pages)
Ignoring the ribbon, the edit page is actually pretty simple. It shouldn't be too difficult to create a custom one, that has the submittal behavior you are interested in. Indeed, since you are keeping the exact same field names and input types, you may be able to simply inherit the default form in yours, and simply override the post call.
I suppose it might be possible instead for you to write some javascript to hijack the submit post of the default edit page, but this seems messy to me, and I probably wouldn't go that route.
If you don't need to complete this task today, I've been meaning to push to github some code I wrote a few months ago. That code is a custom aspx edit/new/display page that is extremely easy to customize / implement. I could forward you the link tonight when I get out of work.