Bug 1328663 - selection list of fact fields are ordered randomly (not dictionary order) in GDT and test scenario editor
Summary: selection list of fact fields are ordered randomly (not dictionary order) in...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Paulo Rego
QA Contact: Jiri Locker
URL:
Whiteboard:
Depends On:
Blocks: 1330390
TreeView+ depends on / blocked
 
Reported: 2016-04-20 01:47 UTC by Hiroko Miura
Modified: 2020-03-27 19:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1330390 (view as bug list)
Environment:
Last Closed: 2020-03-27 19:12:40 UTC
Type: Bug


Attachments (Terms of Use)
sample fact model (3.10 KB, application/zip)
2016-04-20 01:55 UTC, Hiroko Miura
no flags Details

Description Hiroko Miura 2016-04-20 01:47:59 UTC
Description of problem:
When selecting fact field in guided decision table and test scenario,
it's ordered randomly (not dictionary order).
Therefore, if fact has many fields and some of them are very similar each other,
it's a really hard to find/select target field, especially if field name length is long.

These are get listed by dictionary order in 6.0.x/6.1.x business central.

So this is regression in 6.2.0 and later. 


Version-Release number of selected component (if applicable):
6.2.0


Steps to Reproduce:
1. upload Data Model into business central or create it 
2. edit package-names-white-list appropriately (if needed)
3. set dependencies in Project Editor (if needed)
4. create test scenario and add import of fact class via Config tab
5. In editor, add New input by clicking icon left of 'GIVEN', then click 'Add a Filed' link.

Actual results:
fields are listed by random(?) order

Expected results:
fields are listed by dictionary order


Additional info:

Comment 1 Hiroko Miura 2016-04-20 01:55:50 UTC
Created attachment 1148830 [details]
sample fact model


Note You need to log in before you can comment on or make changes to this bug.