Hi Michael,
I unfortunately do not have such a list. My first attempt was to import in v10 a modified export of a v12 VARA.SEC.SQL object. I then got this error:
https://us.v-cdn.net/5019921/uploads/editor/09/hl9n6igu1mg3.png" width="448">
However, I just tried in v11.2 and the import was successful... So it would not seem there would be changes between v11.2 and v12, but rather between v10 and these 2 versions.
I did a bit of further testing - created the same objects in 3 versions : v10.0.8, v11.2.2 and v12.0, exported them and compared the 3 xml files with Notepad++.
V10 vs v11.2
1 - Of course the
<uc-export clientvers=> contained different values
2 -
<VARA OVD_VRName=> contained 2 additional parameters in v10 : '
client=' and '
system='
V10<VARA OVD_VRName="FREI" client="0022" data_type="SQLI_SEC" name="VARA.SEC_SQLI.SAA.EXPORTED" replacementmode="2" system="WS10">
V11.2<VARA OVD_VRName="FREI" data_type="SQLI_SEC" name="VARA.SEC_SQLI.SAA.EXPORTED" replacementmode="2">
3 - There were also these additional tags in v10 :
<Created>Antoine Sauteron on: 2016-12-09 08:20:11</Created>
<Modified>Antoine Sauteron on: 2016-12-09 08:22:23 4 x</Modified>
<LastUsed/>
V11.2 vs v12
Exports looked almost the same.
1 - Once again values of
'clientvers=' differed as expected.
2 - There was this error message in the <infobar> tag in V12 export:
<infobar>U04002751 Attention: There is a variable-replacement restriction in case of security limits (SQLVAR_SECURITY_LEVEL)!</infobar>
The import in v11.2 worked fine after changing the client version, but failed in v10 with the error above (screenshot).
After changing this to "
<infobar/>" (I discovered the '/' means that the tag's content should not be filled) and adjusting the clientvers= field the import in v10 was finally successful.
Conclusion
1- There are a few additional tags and values in v10 :
- 'client=' and 'system=' in the tag corresponding to the object type - VARA in our example.
- <Created>, <Modified> and <LastUsed>.
They can be safely discarded as an xml file that does not contain them could be imported.
2 - No noticeable discrepancies between v11.2 and v12 exports in this case.
3 -The infobar message seemingly caused the import issue in V10 (maybe because of the different length of U codes ?).