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 CreatePrimaryItem - SUBMITTER field required a valid user error
CreatePrimaryItem - SUBMITTER field required a valid user error
CMS-XML Using the UUID for createdBy during createPrimaryItem web service no longer works in SBM 11.5
Using the UUID for createdBy during createPrimaryItem web service no longer works in SBM 11.5
CMS-XML 6.6.1.0.2 - Calling out of TT with CreatePrimaryItem causes an "InValid URL" error message.
6.6.1.0.2 - Calling out of TT with CreatePrimaryItem causes an "InValid URL" error message.
CMS-XML CreateAuxItem and CreatePrimaryItem method with Journal field set to Append.
CreateAuxItem and CreatePrimaryItem method with Journal field set to Append.
CMS-XML Cannot insert 0 into numeric field with CreatePrimaryItem webservice.
Cannot insert 0 into numeric field with CreatePrimaryItem webservice.
CMS-XML Extended fields are duplicated in the TransitionItem and CreatePrimaryItem web service method for sbmappservices72
Extended fields are duplicated in the TransitionItem and CreatePrimaryItem web service method for sbmappservices72
CMS-XML Email Submit and CreatePrimaryItem via Webservice: Journal, Append only field does not populate with any data.
Email Submit and CreatePrimaryItem via Webservice: Journal, Append only field does not populate with any data.
CMS-XML How to input an ExtendedFieldList element for an orchestration is a webservice call
e.g. CreatePrimaryItem on the Data Mapping by default there are zero records for the ExtendedFieldList. This is an array and so you right click on the extenedFieldList[ ] and select "Add Array Record".
CMS-XML Orchestration - Calculate step - binary field value is not set on createnewitem
When using CreatePrimaryItem operation (sbmappservices72), Settings binary-type field value is ignored.
CMS-XML Webservice CreateItem/UpdateItem truncates Description
If there is a field with a LOGICAL name of "Description", then any length settings for this field are applied to the system Description field When using CreatePrimaryItem (or any of the create/update calls), the "Details" field (urn:Description) will be truncated according to the field with logical name "Description" - in this case urn:title. If the field with a logical name of "Description" has its logical name changed to anything else, the problem goes away.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs