XSD Validation based on attribute type value

Hi,
Can any one tell me how to validate xml element value based on attribute value.
Ex:-
my xml has the elements like this.
<channel>
<meta type="VideoTitle">Harding Park Golf Club</meta>
<meta type="ReleaseDate">Wed, 03 Jan 2018 15:00:00 GMT</meta> </channel> I want to validate the xml based on meta type value using xsd. For "VideoTitle" i would like check for String type and for ReleaseDate" i want to check for date format. Thanks, Raj

Try the below statement in “Competitor Lost To” picklist (IndexedPick2)
IIf (([<ReasonWonLost>] = 'Lost to Competition' AND [<IndexedPick2>] IS NULL), N, [<IndexedPick2>])
after you enter this do sign out and then sign in, then check
PS: You need not change it to lookupvalue, the above statement will work as it is

Similar Messages

Multiple keyfigure from different planning area based on attribute value

Multiple keyfigure from different planning area based on the attribute value of Cost element charac.
I need to obtain the value of the attribute in a fox function. Let me explain it further.
Background :
Planning area -
Charac----
KF
area1 -
Payscale group--- Amount
Cost element------AmountVR
area2--Payscalegroup----KF1
KF2
KF3
Cost Element has an attribute "Type"
Value for attribute "Type" = 1,2,3
Based on the value of the attribute, the corresponding KF needs to be multiplied.
Logic :
If type = 1.
AmountVR = Amount * KF1.
elseif type = 2.
AmountVR = Amount * KF2.
elseif type = 3.
AmountVR = Amount * KF3.
endif.
The problem I'm facing is that I'm not able to read the data of attribute "Type". None of the below statement retrieve the value of the "Type".
TYPE = ATRV(Attribute,COSTELEMENT,CO_AREA)
or
TYPE = ATRV(Attribute,COSTELEMENT)
Could you please help me in reading from a time dependent compounding InfoObject?
Regards,
Raghu

Hi..
Thanx Bindu..
I have actual data for Month days..if i am craeting in same layout it is too large.
that's why i am creating two layouts.
below example for better undersatnding.
Actual:
D1 :D2: D3 :D4 : D5 :D6 : D7   : FULLACT (sume of C(1) sum of d1 to d7))
10 :8 :12 : 10 : 14   : 6 : 10    : 70
Plan:
D1EST : D2EST: D3EST :D4EST :D5EST: D6EST: D7EST: FULLEST (sum of d1 to d7)
10         :10        : 10      : 10      :10       :    10    :     10 :         70
How can i read FULLACT value and that value i have to distribute equally in planing layout and always FULLEST is equal to FULLACT.if not equal i have to throug error message hoe can i setup if you have sample code can you send it to me.
what is your idea....
Edited by: Eyda rose on Jun 4, 2008 4:59 PM

Value 'defaultNs:AddBP2Type' is not allowed for attribute 'type'

Hi All,
I created the wsdl for mobile and I tried to send a SOAP request from Altova XMLSpy. However when I geive the wsdl in 'wsdl file location' I receive the following.
File http://127.0.0.1:8080/B1iXcellerator/exec/dummy/com.sap.b1i.vplatform.scenarios.setup/vPac.sap.B1Mobile/001sap0003_sap.B1Mobile.wsdl is not valid.
Invalid XML schema: 'Value 'defaultNs:AddBP2Type' is not allowed for attribute 'type'.'
Error location: wsdl:definitions / wsdl:types / xs:schema / xs:element / @type
Any Idea?
Vangelis

Hi,
it seems that Altove did not cope with defaultNs prefix that is used for marking default namespace.
just look up in your <xs:schema > tag what namespace prefix is used for your namespace - you shall find there something like this
<xs:schema xmlns:ns0="your.namespace.com" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"
and replace prefix defaultNs with prefix of your namespace (in example above it would be ns0)
There might be several usages of defalutNs iside of WSDL (at least in my case were two) so replace it everywhere using same approach
Best regards, Artem

Attributes missing after XSD validation!

I'm feeding a very simple XML file into an equally simple XSD validator. When it returns, all of my tags are fine, but the attributes are dropped. If I parse the file directly, without validation, the attributes are fine.
I've posted my files online at http://www.pastie.org/507569
Am I doing something wrong here? Is this a bug in my JRE (1.6.0r14)?
Thanks for any help,
Norman

XML
<config blah="5">hello!</config>
XSD
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd" />
<xs:element name="config">
   <xs:complexType>
    <xs:simpleContent>
     <xs:extension base="xs:string">
      <xs:attribute name="blah" type="xs:string"/>
     </xs:extension>
    </xs:simpleContent>
   </xs:complexType>
</xs:element>
</xs:schema>
My code...
SchemaFactory schema_factory = SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI);
Schema schema = schema_factory.newSchema(new File("test.xsd"));
StreamSource xml_source = new StreamSource(new File("test.xml"));
StringWriter xml_bridge = new StringWriter();
StreamResult xml_result = new StreamResult(xml_bridge);
Validator validator = schema.newValidator();
validator.validate(xml_source, xml_result);
System.out.println("Validated to: " + xml_bridge.toString());
Result...
Validated to: <?xml version="1.0" encoding="UTF-8"?><config>hello!</config>

Validation based on view attributes

JDeveloper 11.1.1.x
What is the best practice to create validations based on a view attribute from a view object that is of a level higher in the hierarchy?
For example:
     * Use the departments and employees tables from the hr schema.
     * Create an EO for only the employees table, so not for the department table
     * Create VO's for both tables. You should create the Viewlink manually between both views.
     * In the query for the department, add a calculated field in the query.
     For example : availableSalary : 100000 - (select sum(salary) from employees where department_id = Departments.DEPARTMENT_ID) availableSalary
     * I would like to add a validation on the salary field of the employee EO, that says that the new value shouldn't be bigger then the availableSalary field
     Be aware : that when changing an existing salary, only the difference between the old and new salary should be taken into account
     (This removes the "Compare with View Object Attribute" possibility :-()
     * I also want to use some fields from the departments view in my error message on the salary field of the employees EO.
How can we best tackle these requirements ?
Thank you in advance.
Filip Huysmans.

Filip,
I think you are trying to avoid the lesser cost of a Department Entity by an extremely expensive way to get to the comparison done. Firstly, you wire a view instance with an entity, which is strange as there is no association between the entity and the View Object. So all you would have is to access a method in the AM Impl method that looks up the VO and returns the current row's information you need. This AM method can be referenced from the entity object using groovy to perform the comparison (you see that even this is kind of awkward as it connects the entity to the AM, producing a tight coupling that makes any of your code reviewers shake heads in disbelieve). Assuming the update of the VO updates the entity (Departments EO you don't have), you could follow an association using Groovy to perform the validation (which I think sounds easier to do (though by the small cost of creating an EO)
Btw.:
if you have a ViewLink defined then the transient attribute can be easier calculated using Groovy
10000 - DetailTargeName.sum('Salary');
I would think its less expensive then running a SQL query for each department Id
Frank

Is it possible to regroup data based on attribute value of a tag?

is it possible to regroup data based on attribute value of a tag?

Hi Rajeev,
You can filter records during import if one of the Matching field is of type Lookup.
In your case if you create City as flat lookup table in MDM & maintain lookup values in DM(Just as an example), then you can import only records where city is HYD.
Map Name & City, Then in Match Records tab select both the fields (Combination)
then right click on it & select Filter.. option.
Now new pop up will open where you be able to see ur Lookup table values, from there select HYD and Add
Now in default Import Action, set Create Action for None/None (All other will be skip)
This way you will import only HYD records.
But this is possible only on Lookup fields & not foe Text fields
Hope this will help you
Thanks & Regards,
Mahi

"Schema validation found non-data type errors" error when passing a string value to date field in infopath

Hi,
I have an infopath web brower enabled form. In the form i have a date field.
I am passing the data from the database to that field using the C# code.
But, as the field from database is coming as string, i am getting an error, and i am not able to assign the value.
I get the date value from database as "3/25/2011 12:00:00 AM"
I used the below code:
[CODE]
if (objInfopathFormcData.myRecievedDate != null)
myRoot.SelectSingleNode("/my:myFields/my:field97", NamespaceManager).SetValue(objInfopathFormcData.myRecievedDate);
[/CODE]
I am getting the error as "Schema validation found non-data type errors".
How to set the value for a date field in Infopath.
Thank you

HI,
I fixed it:
Below code is used to fix:
[CODE]
XPathNavigator xfield = null;
DateTime dtmyRecievedDate;
dtmyRecievedDate = Convert.ToDateTime(objInfopathFormcData.myRecievedDate);
if (objFormcData.FcCompletionDate != null)
xfield = myRoot.SelectSingleNode("/my:myFields/my:field97", NamespaceManager);
DeleteNil(xfield);
xfield.SetValue(dtmyRecievedDate.GetDateTimeFormats().GetValue(5).ToString());
// method to delete xsi:nil
private void DeleteNil(XPathNavigator nav1)
if (nav1.MoveToAttribute("nil", "http://www.w3.org/2001/XMLSchema-instance"))
nav1.DeleteSelf();
[/CODE]
Thank you

Material Attribute value display based on cost center value

Hi,
Is it possible to display the material attribute value based on cost center value. I mean for some cost centers I would like to display the value of other characteristic in place of material attribute. I am trying to create a query on MP.
Any info in this regard will be appreciated.
Thank you.
Harshan

Hi Adi,
In Rows, Create a struture. Using New Selection, You can restrict the New Value to the cost center (Restrict again on those some cost centers) and material. And for this New Characteristic, you can have a attribute.

Vivado 2013.4 ERROR: [IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order

Hello,
I just downloaded and installed Vivado 2013.4 on my Xubuntu 12.04 machine. But when I try to add IP from the IP catalog, as in the ug937 Lab1 step2, it fails with obscure error messages (see below).
Here's basically what I did:
-In the Flow Navigator, i select the IP Catalog button.
-In the search field of the IP Catalog, I type DDS.
-then I double-click the DDS Compiler and my error occure.
Please Help,
Jerome.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen_demo.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen_demo.vhd":1]
Analysis Results[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen.vhd":1]
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
set_property target_language Verilog [current_project]
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
sources_1[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen_demo.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen_demo.vhd":1]
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
update_compile_order -fileset sim_1
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/fsm.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/fsm.vhd":1]
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/fsm.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/fsm.vhd":1]
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[HDL 9-1654] Analyzing Verilog file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sim/testbench.v" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sim/testbench.v":1]
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/debounce.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/debounce.vhd":1]
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-2313] Loaded Vivado IP repository '/opt/Xilinx/Vivado/2013.4/data/ip'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-1704] No user IP repositories specified
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
Vivado Commands[Project 1-11] Changing the constrs_type of fileset 'constrs_1' to 'XDC'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
sim_1[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[HDL 9-1654] Analyzing Verilog file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sim/testbench.v" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sim/testbench.v":1]
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-234] Refreshing IP repositories
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/debounce.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/debounce.vhd":1]
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen.vhd":1]
set_property constrs_type XDC [current_fileset -constrset]

We had the same problem when switching to Ubuntu 14.04, and there actually is a solution for it: make sure your locales are set to English.
$> env | grep LC_*
should only show english (or C) locales, all others are known to cause parsing errors in some numbers, usually caused by wrong string-to-float conversions (e.g. 18,29 in german is 18.29 in english). You can change the locales in the file /etc/default/localesThis is not the first time we had problems with the locale settings, Xilinx does not seem to test their software with anything else than en_US, causing obscure bugs like this one.
HTH
Philipp

Invoke different Summary Screen based on attribute value

Hi Experts,
I have a requirement to show different OPA landing summary page based on attribute value received from Siebel application. Is that possible?
For e.g.: Create 2 summary screen
Siebel field value opa_attr1 = A or B, if A I want to display summary screen 1 otherwise display summary screen 2.
Thanks,
Vinay

Thanks you for your reply. The link is not what I want. My case is that I already have a map stored in Oracle database under obiee_navteq schema. I want to use OBIEE to display map by adding different image/icon at different cities based on the value of an attribute column. All the examples I can find is to use measure column as an condition, not by attribute column.
Thanks

Validation on Integer data type attribute

Hi,
Working on jdev 11.1.1.3.0
I have to do validation on integer data type like, it should not allow 13.20(only single digit numbers.).
I am doing validation on AMImpl and converting the int into string
String per=Row.getPer().toString();// here if user enter 13.20, then per containing only 13 so its not going to inside if.
if(StringUtils.contains(per,"."))
return false;
Even i have written regular expression on my field but its working
can any one help me.

Hi,
Why don't you use the af:convertNumber in your tag?
Something like that:
<af:inputText>
<af:convertNumber>
</af:inputText>
Doc: http://download.oracle.com/docs/cd/E12839_01/apirefs.1111/e12419/tagdoc/af_convertNumber.html
Regards,

ADF BC declarative Compare validator on date attributes

Hello
I trying to abandone validation on the UI beans by resorting to the built-in ADF declarative validation available at the Entity object level.
I test the Compare validator between two numeric attributes and it worked well, also between two String attributes, but when i tried to compare two dates attributes the results of the validation was not correct.
any reason as to why Entity based validation based on dates values does not give appropriate results
rgds
Ammar Sajdi

We are using entity based declerative validations for Dates with no problem.
Remember that Date type has also a time portion in database.
may be there is your error.

XSD Validation, checking for required elements

I'm using the FTP Adapter to retrieve a flat file in a format like this -
H|1|1234|5-APR-2007
L|1|33123|2
L|1|12345|1
L|1|6969|5
S|1|Milton Park, Abingdon, OX142NF
I have generated an XSD file using the built in wizard that looks like this -
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
targetNamespace="http://bpelns.corp.rmd.org/complex"
xmlns:tns="http://bpelns.corp.rmd.org/complex"
elementFormDefault="qualified"
attributeFormDefault="unqualified" nxsd:encoding="ASCII" nxsd:stream="chars" nxsd:version="NXSD">
<xsd:element name="order">
<xsd:complexType>
<xsd:choice minOccurs="1" maxOccurs="unbounded" nxsd:choiceCondition="terminated" nxsd:terminatedBy="|">
<xsd:element name="HEADER" minOccurs="1" maxOccurs="1" nillable="false" nxsd:conditionValue="H">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDERID" nillable="false" minOccurs="1" maxOccurs="1" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="|" nxsd:quotedBy=""">
</xsd:element>
<xsd:element name="CUSTOMERID" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="|" nxsd:quotedBy=""">
</xsd:element>
<xsd:element name="ORDERDATE" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="${eol}" nxsd:quotedBy=""">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="LINEITEM" minOccurs="1" maxOccurs="unbounded" nxsd:conditionValue="L">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDERID" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="|" nxsd:quotedBy=""">
</xsd:element>
<xsd:element name="PRODUCTCODE" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="|" nxsd:quotedBy=""">
</xsd:element>
<xsd:element name="QUANTITY" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="${eol}" nxsd:quotedBy=""">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="SHIPPING" minOccurs="1" maxOccurs="1" nxsd:conditionValue="S">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDERID" type="xsd:int" nxsd:style="terminated" nxsd:terminatedBy="|" nxsd:quotedBy=""">
</xsd:element>
<xsd:element name="ADDRESS" type="xsd:string" nxsd:style="terminated" nxsd:terminatedBy="${eol}" nxsd:quotedBy=""">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:schema>
I added the various minOccurs & maxOccurs attributes. I would like to be able to state that the element HEADER is required. However, despite the min & max values it carries straight through to the next point in the BPEL flow. I cannot use the required attribute type, as JDeveloper does not recognise this.
How can I acheive the validation I require ? Is the XSD the right place to be doing it (I thought so, as it is the schema definition) ? If I cannot do this with the XSD how else might I acheive it in a concise way, ie not using a big switch operation to test various elements.

I have just noticed that the XSD is creating the following XML document, which explains the validation failure. After the header it is treating everything else as a line item.
<?xml version="1.0" encoding="UTF-8" ?>
<order xmlns="http://bpelns.corp.rmd.org/complex">
<HEADER>
<ORDERID>1</ORDERID>
<CUSTOMERID>1234</CUSTOMERID>
<ORDERDATE>5-APR-2007</ORDERDATE>
</HEADER>
<LINEITEM>
<ORDERID>1</ORDERID>
<PRODUCTCODE>33123</PRODUCTCODE>
<QUANTITY>2</QUANTITY>
</LINEITEM>
<LINEITEM>
<ORDERID>L</ORDERID>
<PRODUCTCODE>1</PRODUCTCODE>
<QUANTITY>12345|1</QUANTITY>
</LINEITEM>
<LINEITEM>
<ORDERID>L</ORDERID>
<PRODUCTCODE>1</PRODUCTCODE>
<QUANTITY>6969|5</QUANTITY>
</LINEITEM>
<LINEITEM>
<ORDERID>S</ORDERID>
<PRODUCTCODE>1</PRODUCTCODE>
<QUANTITY>65 Milton Park, Abingdon, OX142NF</QUANTITY>
</LINEITEM>
</order>

Change field value in a table, based on another field value in the same row (for each added row)

Please Help, I want to change field value in a table, based on another field value in the same row (for each added row)
I am using this code :
<HTML>
<HEAD>
<SCRIPT>
function addRow(tableID) {
var table = document.getElementById(tableID);
var rowCount = table.rows.length;
var row = table.insertRow(rowCount);
var colCount = table.rows[0].cells.length;
for(var i=0; i<colCount; i++ ) {
var newcell = row.insertCell(i);
newcell.innerHTML = table.rows[1].cells[i].innerHTML;
switch(newcell.childNodes[0].type) {
case "text":
newcell.childNodes[0].value = "";
break;
case "checkbox":
newcell.childNodes[0].checked = false;
break;
case "select-one":
newcell.childNodes[0].selectedIndex = 0;
break;}}}
function deleteRow(tableID) {
try {var table = document.getElementById(tableID);
var rowCount = table.rows.length;
for(var i=0; i<rowCount; i++) {
var row = table.rows[i];
var chkbox = row.cells[0].childNodes[0];
if(null != chkbox && true == chkbox.checked) {
if(rowCount <= 2) {
alert("Cannot delete all the rows.");
break;}
table.deleteRow(i);
rowCount--;
i--;}}}catch(e) {alert(e);}}
</SCRIPT>
</HEAD>
<BODY>
<INPUT type="button" value="Add Row" onClick="addRow('dataTable')" />
<INPUT type="button" value="Delete Row" onClick="deleteRow('dataTable')" />
<TABLE id="dataTable" width="350px" border="1">
<TR>
<TD width="32"></TD>
<TD width="119" align="center"><strong>Activity</strong></TD>
<TD width="177" align="center"><strong>Cost</strong></TD>
</TR>
<TR>
<TD><INPUT type="checkbox" name="chk"/></TD>
<TD>
<select name="s1" id="s1">
<option value="1">1</option>
<option value="2">2</option>
<option value="3">3</option>
</select>
</TD>
<TD><input type="text" name="txt1" id="txt1"></TD>
</TR>
</TABLE>
</BODY>
</HTML>

Hi,
Let me make sure u r working with table control.
First u have to create a event(VALIDATE) to do the validation.
Inside the event,
1. First get the current index where user has pointed the curson
2. Once u get the index read the internal table with index value.
3. Now u can compare the col1 and col2 values and populate the error message.
1. DATA : lo_elt TYPE REF TO if_wd_context_element,
l_index type i.
lo_elt = wdevent->get_context_element( name = 'CONTEXT_ELEMENT' ).
CALL METHOD LO_ELT->GET_INDEX( RECEIVING MY_INDEX = l_index.
above code should be written inside the event.
Thanks,

Not able to import Attribute Text Values in Taxonomy table

Hi Experts,
I have an excel file with 54K records of Attribute text values need to import in to taxonomy table. my excel file has 3 fields like ID, Name, Text Values. While mapping the fields in feild mapping grid, I have mapped ID field with Attribute Alias, Name with Attribute name, Text Value with Text Value and clone field of Text Value with [Text Value Remote Key]. Based on the field mapping I was trying to map values for ID filed with Attribute Alias field. Here I found Attribute Alias field has values in destination grid which were imported before for Attribute Name ID's in to the Alias field for attribute names.
Here I found these values are different when I tried to map these values and the Value map buttons(Automap/Map/Add) were disabled.
in the same way I tried with out maping the values for Attribute value id and selected the Attribute Alias field as value mapping field. but here in the import actions tab the records are active and disabled the import action option.
so I have executed the import process, but no attribute text values were imported in to Taxonomy table.
I am using the MDM 7.1 with build version 7.1.01.46.
Please let me know if anyone came across this situation.
Thanks,
RDNPrasad

problem solved

XSD Validation based on attribute type value

Similar Messages

Maybe you are looking for