Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Sub-Relational field values are shown as UUID's in Form Actions configuration dialog
2) Add Single-Selection/Multi-Selection field to table with some custom values defined in field property editor; 3) Add Single- Relational field to same table and map it to same table (as it set by default); 4) Add Sub-Relational field to same table and map it to previously configured Single-Relational field in same table and set Single-Selection/Multi-Selection field as Sub-Field;
CMS-XML Form action does not work with sub-relational field
Steps to reproduce 1) In SBM Composer, create a Single Selection field called "Field A". Add "x", "y" and "z" values 2) Create a Single Relational field called "Field B" and make it point to the current primary table
CMS-XML Form action does not evaluate "(None)" value as empty when checking rule of "Is Field Empty"
Form actions and rules used in form actions are not evaluating the "(None)" value in relational, multi-relational, and sub-relational fields as empty when checking "Is Field Empty".
CMS-XML Relational fields are treated as not empty on a Form Action because '(None)' is being seen as a value
enable 'text field is not empty' text field And pop up ' relational field is not empty' Else
CMS-XML Form Action Support for System relational fields
Form Action Support for System relational fields
CMS-XML Rest Grids do not work with Sub-Relational fields in 10.1.2 (Example: PDF Widget)
1. Have two Process apps (A and B), A is referenced to B and has a Single-Relational and Sub-Relational field. 2. Have a form (Submit form ) on A process app with RestGrid that uses Sub-Relational field as a parameter 1. Try to submit an A item.
CMS-XML Disabled Multi-Relational or Multi-Selection field on form causes data loss
If you disable a multi- relational field on a transition form using a form action , transitioning the item will clear all selected values in the multi- relational field .
CMS-XML SetMultiListValues does not fire change event for single or multi select and relational fields
Workaround: Use form actions Manually call FireChangeEvent on the independent field(s).
CMS-XML A blank/empty Change History entry is recorded on the Child record when a Transition Action moves the Parent item from Submit
The submit transition is a called "Child Submit". " Set original item in new item's field" is set to a relational field that will hold the parent. All fields are mapped.
CMS-XML Subrelational field value does not display value when updating from a relational field value that initially had no value in the subrelational field
Sub-relational field value does not display value when updating from a relational field value that initially had no value in the sub-relational field ... Select a relational value where one of its sub-relational fields has a null or empty string value . ... Open the form again (via update) and select a different relational value . The sub-relational field that was empty before is now empty regardless of what you select for the Relational field
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Working with Items, Part 2 (demonstration)
This Dimensions CM demonstration shows you how to copy item revisions to a work area using the Get and Update commands, deliver a modified file from a work area to a stream using the Deliver command, and action an item revision

Additional Assistance

  • Submit a Case Online
  • FAQs