295 views

Description

When multiple form section records for the same table/view/caption exist on an instance (for example, Table = incident, View = Default view, Caption = NULL), only one is used when the form is rendered and personalized/configured.

Steps to Reproduce

  1. Identify two instances with the same set of duplicate form section records (e.g. Table = incident, View = Default view, Caption = NULL).
  2. On the source instance, create an update set and capture form section updates (e.g. change the order of fields or add/remove a field).
  3. Complete the update set and retrieve it on the target instance.

Compare the update records in the update set on source and target instance. There may be an update record referencing a different form section record in both the update name and XML payload (the sys_id in the name and payload is changed when the update set is being retrieved).

Workaround

Remove the unused form section records. To identify used form section records:

  • Look at the sys_id of a form section update in the update set that captured the customizations.
  • Open the form in question and use source view or form inspector to find the HTML tag similar to:
    <div id="bf1d96e3c0a801640190725e63f8ac80" class="section-content" glide="true">. This usually shows up just bellow <div id="header_attachment"></div>.

Note: Subscribe to this known error article (click Subscribe button at the top of the article) to receive notifications when more information is available about this issue.

 


Related Problem: PRB637728

Seen In

Fuji Patch 3
Fuji Patch 5
Fuji Patch 6
Fuji Patch 7 Hot Fix 5
Fuji Patch 8

Fixed In

Fuji Patch 11
Geneva Patch 1
Helsinki

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2016-03-31 15:00:41
Published:2015-07-20