search

moxter / mxupdate-archive

Automatically exported from code.google.com/p/mxupdate
1 stars 0 forks source link

When orderding web form's field should not follow only name #168

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. export OOTB CI (e.g. type_CustomerPartNumber)
   from CI file you can see that orderFields is nowadays following name of field only
2. import CI back to schema
   as there are same name (e.g. 'Name') used by two places...
   - by label: 'emxMaterialComplianceCentral.Common.Name' with expression '$<name>'
   - by label: 'emxMaterialComplianceCentral.Common.Name' with expression '$<relationship[relationship_CustomerEquivalent].from.name>'
   ...order after import will not be as originally was after OOTB installation from original installation scripts

What is the expected output? What do you see instead?
   order of fields will be correctly placed

What version of the product are you using? On what operating system?
   Enovia V6R2012x.HF11
   MxUpdate Update Deployment Tool V0.10.0 (with latest revision 854 and unOfficial fix)

Please provide any additional information below.
   should it be combination of different settings when ordering fields
   unluckily also label can be same there in multible fields, also expression can be empty
   maybe combination of name, label and expression of field could be enough?

Original issue reported on code.google.com by yrtti...@gmail.com on 23 May 2012 at 12:34

GoogleCodeExporter commented 8 years ago 
workaround (or even actually the solution): remove whole content of 
'orderFields' from CI file

another issue with OOTB definitions, there are fields that are having empty as 
'name' of field (e.g. 'ECNContextPartSearchForm')

solution proposal: when exporting form place value e.g. 'DummyField1' ... 
'DummyField<n>' to those where field name is empty
...this is tested doing modifications manually, and works

Original comment by yrtti...@gmail.com on 24 May 2012 at 4:33

GoogleCodeExporter commented 8 years ago

Original comment by tim.mox...@innobix.com on 7 Feb 2014 at 8:31