Forum Discussion
TEXAS_COMPTROLL_1
13 years agoOccasional Contributor
We have also had this problem for almost a year. I tried the beta 4 version and the problem is still there.
The symptoms are that adding elements in the form view does not add them in the schema order. You have to manually go to the xml view and cut and paste to get it in the correct order.
This defeats the whole purpose of buying the Pro version for us, since it is being used by business users who don't know how to edit xml and want to use the form view. I'm not sure why there haven't been more reports of this, since it seems to be a pretty serious problem.
Here is an example of the type of sequence that will not be conformed to:
I've noticed also that the form view displays elements in the order according to the schema, not the order of the actual xml. So its confusing, because everything looks good in the form view, but when you look at the actual xml, it is out of order. This requires a technical person to go in and edit xml for many test cases.
The symptoms are that adding elements in the form view does not add them in the schema order. You have to manually go to the xml view and cut and paste to get it in the correct order.
This defeats the whole purpose of buying the Pro version for us, since it is being used by business users who don't know how to edit xml and want to use the form view. I'm not sure why there haven't been more reports of this, since it seems to be a pretty serious problem.
Here is an example of the type of sequence that will not be conformed to:
<xsd:element maxOccurs="1" minOccurs="1" name="TXCommonData" type="TXCommonType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Form05-102" type="TXFranchisePubInfoReportCType"/>
<xsd:element maxOccurs="1" minOccurs="0" name="Form05-158A" type="TXFranchiseTaxReportACType"/>
<xsd:element maxOccurs="1" minOccurs="0" name="Form05-158B" type="TXFranchiseTaxReportBCType"/>
<xsd:element maxOccurs="1" minOccurs="0" name="Form05-160" type="TXCreditsSummaryScheduleCType"/>
<xsd:element maxOccurs="1" minOccurs="0" name="Form05-163" type="TXFranchiseNoTaxDueReportCType"/>
<xsd:element maxOccurs="1" minOccurs="0" name="Form05-164" type="TXFranchiseExtRequestCType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Form05-165" type="TXFranchiseExtAffilListCType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Form05-166" type="TXFranchiseAffiliatesScheCType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Form05-167" type="TXOwnershipInfoReportCType"/>
<xsd:element maxOccurs="1" minOccurs="0" name="Form05-169" type="TXFranchiseTaxReportEZCType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="Form05-175" type="TXFranchiseTieredParReprtCType"/>
I've noticed also that the form view displays elements in the order according to the schema, not the order of the actual xml. So its confusing, because everything looks good in the form view, but when you look at the actual xml, it is out of order. This requires a technical person to go in and edit xml for many test cases.
Related Content
- 2 months agoStoplight