SBL-EAI-04267: XSLT Processing Exception: %1

Applies to:

Siebel CRM Call Center - Version: 7.7.2.7 SIA [18376] - Release: V7

Information in this document applies to any platform.



Symptoms

When using exslt:node-set() function in the XSLT with the EAI XSLT Transport Business Service, the following error occurs:



XSLT Processing Exception: The specified function is not available: http://exslt.org/common:node-set(SBL-EAI-04267)

--

Error invoking service 'EAI XSLT Service', method 'Transform' at step 'XSLT Conversion Response'.(SBL-BPR-00162)



Cause

The EAI XSLT Service Business Service supports the Apache XALAN API and the actual DLL, which the class CSSXSLTService of this BS references is XALAN-C_*.DLL. And this XSLT processor does not support the extension node-set() with the namespace http://exslt.org/common.



Solution

To use the nodeset extension, use the nodeset() function in the namespace xmlns:xalan=http://xml.apache.org/xalan



For example,



version="1.0"
xmlns:xalan="http://xml.apache.org/xalan"
exclude-result-prefixes="xalan">

...











References

BUG:10515265 - BOOKSHELF DOES NOT CONTAIN ENOUGH INFORMATION OF SUPPORTED XSLT PARSERS.



























Applies to:

Siebel System Software - Version: 7.8.2.3 SIA [19221] - Release: V7

Sun Solaris SPARC (64-bit)

Product Release: V7 (Enterprise)

Version: 7.8.2.3 [19221] Com/Med

Database: Oracle 9.2.0.6

Application Server OS: Sun Solaris 9

Database Server OS: Sun Solaris 9



This document was previously published as Siebel SR 38-3178851373.

Symptoms

SBL-EAI-04267

Below is a piece from the XSLT being used :-











//







When trying to make use of this XSLT in Siebel, I get the following error message,



(xsltransform.cpp (573)) SBL-EAI-04267: XSLT Processing Exception: The specified function is not available: http://www.w3.org/2005/xpath-functions:current-dateTime



When transformation is done in XMLSpy it is working fine. This may be because that function is not one of the "core" Xpath functions that all implementations must support "http://www.w3.org/TR/xpath#corelib" . i.e. it's an optional one, that XMLspy supports, but Siebel doesn't.



Please provide your suggestions, is there any workaround for Siebel XSLT Service to adopt this functionality.





Cause

The error that customer has indicated has been reproduced. However, the error that is observed is as follow. This is opposed to what customer is getting.



XSLT Processing Exception: Could not find function: current-dateTime()

pattern = 'current-dateTime()'

Remaining tokens: ('current-dateTime' '(' ')')(SBL-EAI-04267)



Change Request 12-1GKP3RF has been logged to address this.



Solution

If the function is not used, the error is not reported.

























Applies to:

Siebel System Software - Version: 7.8.2.3 [19221] - Release: V7

z*OBSOLETE: Microsoft Windows 2000

Product Release: V7 (Enterprise)

Version: 7.8.2.3 [19221]

Database: Oracle 9.2.0.6

Application Server OS: Microsoft Windows 2000 Server

Database Server OS: Sun Solaris 7



This document was previously published as Siebel SR 38-3233419145.

Symptoms

SBL-EAI-04267, SBL-BPR-00162

Requirement is to read a XSLT file and transform a XML file using the EAI XSLT Service. The XSLT file has a function Ext:transform_lov defined within it which it calls whenever it hits a node name starting with "LOV_".



On execution, the following error was encountered.....



“Error invoking service 'EAI XSLT Service', method 'Transform' at step 'Execute Transformation'.(SBL-BPR-00162)

--

XSLT Processing Exception: The specified function is not available: Ext:transform_lov(SBL-EAI-04267)”



It seems that it's complaining about the xmlns:Ext="Ext" declared in the beginning of the XSLT.



Please find attached the following :



XSLT : lovdatamap.xslt

Source XML : test_a1.xml

Target XSD : dest.xsd



Please advise.





Cause

The "xsl:function" is available for XSLT version 2.0. However, the underlying XSLT processor (Apache Xalan-C 1.5) used by EAI XSLT Service supports version 1.0. As such, the functions that are available in XSLT version 2.0 will not work in Siebel application.



Solution

Change Request 12-1HMLWRR has been logged to request for this information to be documented in Siebel Bookshelf.



Additional Keywords:

error when using XSL functions, not supported

תגובות

הוסף רשומת תגובה

פוסטים פופולריים מהבלוג הזה

Profile Attributes and Open UI

תמונה
Yes, Profile Attributes! As the ever attentive, up-to-date Siebel CRM expert that you are when you read this, you know that in Siebel Open UI (since version 15), it is no longer allowed/supported to  set  Profile Attributes from browser-side script. But  getting  them is not a problem, since the  GetProfileAttr  function works perfectly fine. Recently I found a few vanilla Profile Attributes that came quite handy in my work in Open UI JavaScript: Navigation Type : stores the navigation type such as "NAVIGATION_TAB" ActiveViewName : does what it says on the tin IsOpenUI : returns "1" when the application runs in Open UI Is SUI Theme : when "TRUE", the application theme is Synergy (aka SUI) Position:  returns the currently active position Primary Responsibility Name : guess what this one is… Profile Image : returns the URL of the user's profile image Org.Name : returns the name of the user's organization Here's a sample line of ...
המשך לקרוא

SBL-BPR-00191: The rowId of the active row of the primary buscomp '%1', '%2', does not match the Primary Id

Applies to: Product Release: V7 (Enterprise) Version: 7.5.3 [16157] ESN Database: Oracle 9.2.0.2 Application Server OS: Microsoft Windows 2000 Server SP 3 Database Server OS: Microsoft Windows 2000 Server SP 3 This document was previously published as Siebel SR 38-1386997031. Symptoms SBL-BPR-00191 We have a error with a workflow. This WF is excuted by policy when a particular activity is closed. The WF Business Object is 'Action'. Inside this WF, there is a subprocess that invokes a Business Service that creates a new activity. In a second subprocess, the region Id of this new activity is updated using the standar update method funcionality of Siebel workflow process. Error processing Siebel Operation for: Business Object 'Action' Business Component 'Action' Primary Id ''1-5NEI6' Operation 'Insert'(SBL-BPR-00100) -- The rowId of the active row of the primary buscomp 'Action', '1-4SNCV', does not match the Prima...
המשך לקרוא

SBL-SVC-00150

Applies to: Siebel CRM - Version: 7.5.3 [16157] and later   [Release: V7 and later ] z*OBSOLETE: Microsoft Windows 2000 Product Release: V7 (Enterprise) Version: 7.5.3 [16157] Database: IBM DB2/UDB 7.2 Application Server OS: Microsoft Windows 2000 Advanced Server SP 2 Database Server OS: IBM AIX 4.3.3 This document was previously published as Siebel SR 38-1153677971. Symptoms SBL-SVC-00150In callcenter (development environment) Group News administration > All News, when the ‘Status’ field of a news story is changed from ‘Submitted’ to ‘Completed’, the following error pops up. You cannot change the current field’s value from ‘Submitted’ to ‘Completed’. Rule validation failed: ‘[Total Approvers] = 0’ (SBL-SVC-00150) When the status field of a news story is changed from ‘Submitted’ to ‘Pending Approval’, the following error pops up. You cannot change the current field’s value from ‘Submitted’ to ‘Pending Approval’. R...
המשך לקרוא