Applies to
  • SITS:Vision v8.7.0
  • Uniface v9.6.03
  • Microsoft Windows 7
  • Microsoft SQL Server 2012 (SP1) - 11.0.3128.0

What?
"Quick" may not be the right word, so this is a somewhat summarized article on how to get data out of SITS, up to running the monitors and populating an OUTPUT table in the SITS database. Note that this does not include steps thereafter in the Staging or Target destination which will be specific to your business requirements.

Why?
If you're developing in SITS, and you use the client, the first time(s) you do this, the task is rather daunting. Having done it a few times and run through a few, I thought I'd note this down to remind me if I ever work for a company using SITS:Vision again.

How?

What?
An article on how to declare an XML element as NULL using the attribute "xsi:nil". I'm going to use a very short example by providing a blank date of birth value:
copyraw
-- What I have:
<DATE_OF_BIRTH />
<DATE_OF_BIRTH_EUROPEANFORMAT>//</DATE_OF_BIRTH_EUROPEANFORMAT>

-- What I want:
<DATE_OF_BIRTH xsi:nil="true" />
<DATE_OF_BIRTH_EUROPEANFORMAT xsi:nil="true" />
  1.  -- What I have: 
  2.  <DATE_OF_BIRTH /> 
  3.  <DATE_OF_BIRTH_EUROPEANFORMAT>>//</DATE_OF_BIRTH_EUROPEANFORMAT> 
  4.   
  5.  -- What I want: 
  6.  <DATE_OF_BIRTH xsi:nil="true" /> 
  7.  <DATE_OF_BIRTH_EUROPEANFORMAT xsi:nil="true" /> 

Why?
Outputting from SITS:Vision to our staging environment, the application would only output blank values using single tags so we had to find a place to introduce it. On strings this has little worth, but on dates which could be NULL, this was necessary (unless we interpreted dates as strings which we don't want to do):
Category: XML Stylesheet Language Transformations :: Article: 578

XSD Elements
Element Explanation
all Specifies that the child elements can appear in any order. Each child element can occur 0 or 1 time
annotation Specifies the top-level element for schema comments
any Enables the author to extend the XML document with elements not specified by the schema
anyAttribute Enables the author to extend the XML document with attributes not specified by the schema
appinfo Specifies information to be used by the application (must go inside annotation)
attribute Defines an attribute
attributeGroup Defines an attribute group to be used in complex type definitions
choice Allows only one of the elements contained in the declaration to be present within the containing element
complexContent Defines extensions or restrictions on a complex type that contains mixed content or elements only
complexType Defines a complex type element
documentation Defines text comments in a schema (must go inside annotation)
element Defines an element
extension Extends an existing simpleType or complexType element
field Specifies an XPath expression that specifies the value used to define an identity constraint
group Defines a group of elements to be used in complex type definitions
import Adds multiple schemas with different target namespace to a document
include Adds multiple schemas with the same target namespace to a document
key Specifies an attribute or element value as a key (unique, non-nullable, and always present) within the containing element in an instance document
keyref Specifies that an attribute or element value correspond to those of the specified key or unique element
list Defines a simple type element as a list of values
notation Describes the format of non-XML data within an XML document
redefine Redefines simple and complex types, groups, and attribute groups from an external schema
restriction Defines restrictions on a simpleType, simpleContent, or a complexContent
schema Defines the root element of a schema
selector Specifies an XPath expression that selects a set of elements for an identity constraint
sequence Specifies that the child elements must appear in a sequence. Each child element can occur from 0 to any number of times
simpleContent Contains extensions or restrictions on a text-only complex type or on a simple type as content and contains no elements
simpleType Defines a simple type and specifies the constraints and information about the values of attributes or text-only elements
union Defines a simple type as a collection (union) of values from specified simple data types
unique Defines that an element or an attribute value must be unique within the scope

XSD Restrictions/Facets for Datatypes
Constraint Description
enumeration Defines a list of acceptable values
fractionDigits Specifies the maximum number of decimal places allowed. Must be equal to or greater than zero
length Specifies the exact number of characters or list items allowed. Must be equal to or greater than zero
maxExclusive Specifies the upper bounds for numeric values (the value must be less than this value)
maxInclusive Specifies the upper bounds for numeric values (the value must be less than or equal to this value)
maxLength Specifies the maximum number of characters or list items allowed. Must be equal to or greater than zero
minExclusive Specifies the lower bounds for numeric values (the value must be greater than this value)
minInclusive Specifies the lower bounds for numeric values (the value must be greater than or equal to this value)
minLength Specifies the minimum number of characters or list items allowed. Must be equal to or greater than zero
pattern Defines the exact sequence of characters that are acceptable
totalDigits Specifies the maximum number of digits allowed. Must be greater than zero
whiteSpace Specifies how white space (line feeds, tabs, spaces, and carriage returns) is handled
Source(s):

Applies to:
  • Microsoft Windows 7 Enterprise
  • SITS:Vision Students (v8.7.0)
What?
You might be able to work it out from the online manuals but it took me a while, we wanted to bring back both the code and the lookup value in our XML to our Staging environment.

Why?
Let's take the country of birth of a person as an example as it is expected to be a long list and where just using the parameter &S is not workable. Instead I want to use &G[] and get both the code and the lookup value:
copyraw
-- What I have: no export format
<stu_codc>5826</stu_codc>

-- What I could have: export format set to get lookup value
-- &GCOD_NAME.COD.SRS
<stu_codc>England</stu_codc>

-- What I want: export format to get multiple values
-- &G[COD.SRS:•<•<COD_CODE.COD•>•>|•<•<COD_NAME.COD•>•>]
<stu_codc>5826|England</stu_codc>
  1.  -- What I have: no export format 
  2.  <stu_codc>5826</stu_codc> 
  3.   
  4.  -- What I could have: export format set to get lookup value 
  5.  -- &GCOD_NAME.COD.SRS 
  6.  <stu_codc>England</stu_codc> 
  7.   
  8.  -- What I want: export format to get multiple values 
  9.  -- &G[COD.SRS:<<COD_CODE.COD•>>|•<<COD_NAME.COD•>>] 
  10.  <stu_codc>5826|England</stu_codc> 

How?
Category: Extensible Markup Language :: Article: 575

What?
Trying to export a STU record but I want to use the XET template I created rather than the pre-installed XML export formats. When I try to export using data format XET, the system has never heard of it.

Why?
To test the XET I created, I want to see what the resulting XML will look like so that my post-staging phase can be developed as it will know what the data and label fields look like.

How?

Credit where Credit is Due:


Feel free to copy, redistribute and share this information. All that we ask is that you attribute credit and possibly even a link back to this website as it really helps in our search engine rankings.

Disclaimer: Please note that the information provided on this website is intended for informational purposes only and does not represent a warranty. The opinions expressed are those of the author only. We recommend testing any solutions in a development environment before implementing them in production. The articles are based on our good faith efforts and were current at the time of writing, reflecting our practical experience in a commercial setting.

Thank you for visiting and, as always, we hope this website was of some use to you!

Kind Regards,

Joel Lipman
www.joellipman.com

RSS Feed

Related Articles

Joes Revolver Map

Joes Word Cloud

google   data   zoho   mysql   field   parameter   following   server   order   uploaded   website   file   client   version   user   function   form   date   database   code   system   used   windows   creator   need   time   page   note   display   name   where   case   added   table   files   script   value   source   using   license   deluge   create   joomla   work   error   first   would   list   report   find   JoelLipman.Com

Accreditation

Badge - Certified Zoho Creator Associate
Badge - Certified Zoho Creator Associate

Donate & Support

If you like my content, and would like to support this sharing site, feel free to donate using a method below:

Paypal:
Donate to Joel Lipman via PayPal

Bitcoin:
Donate to Joel Lipman with Bitcoin bc1qf6elrdxc968h0k673l2djc9wrpazhqtxw8qqp4

Ethereum:
Donate to Joel Lipman with Ethereum 0xb038962F3809b425D661EF5D22294Cf45E02FebF
© 2024 Joel Lipman .com. All Rights Reserved.