Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Javascript API: disabled checkbox changes are not stored in the database
Javascript API: disabled checkbox changes are not stored in the database
CMS-XML Importing a blueprint allows database name to be changed
marked deleted (or disabled, in the case of states). • The Backfill to existing items check box is not available for Multi-Selection fields. • Some styles options for Numeric and Date/Time fields cannot be changed.
CMS-XML Role allocation view for Users/Groups may not provide visual cues
The Role allocation view for Users/Groups may not provide visual cues upon role allocation and the checkboxes may not have description labels. This happens mostly with databases containing user/group names with diacritics.
CMS-XML Database value is used in fixed precision numeric field instead of display
Database value is used in fixed precision numeric field instead of display
CMS-XML Binary/trinary field won't map successfully to checkbox in PDF widget
For a binary/trinary field that is set to the style = Check box , when mapping the field in the parameters of a pdf widget to a checkbox field in the pdf, the checkbox on the pdf for the item remains unchecked when the value should be checked, even though the value for the sbm field in the item is showing as checked.
CMS-XML Performance very slow when ts_selections has a large number of values
When using actions on selection fields in a database with are large number of ts_selections, performance can suffer.
CMS-XML Import: mapping single select values gives error "Number of bound columns exceeds the number of result columns"
When using the Mashup2009 driver and "import from another SBM database ", you can map the source and destination fields. However, get error "Number of bound columns exceeds the number of result columns" when trying to map the specific values for a single select field. (For example, when trying to map the "new" state in the source to be the "waiting" state in the destination.) State field is just an example.
CMS-XML AppScript method IsFieldEqual always returns False when using Database Field Name
The doc says that IsFieldEqual will accept a field name or a field ID. However, when you use database field name, it always returns False. The correct value is returned when using the ts_id of the field or you use the field name ( not the database field name ), however the field ID changes between environments and the field name could be changed later in composer and inadvertantly breaking your scripts..
CMS-XML Import Data tool in the SBM App Admin needs to be able to set a default value.
The new Import Data tool in the web ui SBM Application Administrator lets you import from an excel file but there isn't a way to set the default value of certain fields. Most important the old "import from database " tool used to let you set the default value for the State field to something like "New" or set other fields to have a default value when you imported.
CMS-XML On multi-selection fields using checkboxes, "on field change" form actions only fire when first option is selected
When MS1 field changes value If MS1 field contains any Option1
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs