Bug 201673 Data Set Editor should not generate Parameter Position for an Named ODA Parameter
It is valid for an ODA data set parameter definition to have a driver-defined (native) name and no position (value = 0). The Data Set Editor currently assumes that this is not valid. It should *not* have automatically assign a derived position ( >0 value) to the data set parameter and issue a user warning message. The warning message in this case is inaccurate. And by assigning a bogus parameter position, it may disable the ability for the Data Engine to use the parameter's native name when interacting with the ODA runtime driver.
UI/org.eclipse.birt.report.designer.ui/src/org/eclipse/birt/report/designer/ui/dialogs/SelectValueDialog.java
DateFormatter formatter = new DateFormatter( ULocale.US );
							formatter.applyPattern( "yyyy-MM-dd HH:mm:ss.S" );
							displayCandiateValue = formatter.format( (Date) candiateValue );
						}
						else
							displayCandiateValue = candiateValue;
						viewerValueList.add( displayCandiateValue.toString( ) );
						selectValueList.add( displayCandiateValue.toString( ) );
					}
				}
			}
			else
			{
				selectValueList.removeAll( );
				modelValueList.clear( );
				viewerValueList.clear( );
				ExceptionHandler.openErrorMessageBox( Messages.getString( "SelectValueDialog.errorRetrievinglist" ), Messages.getString( "SelectValueDialog.noExpressionSet" ) ); 
			}
			if ( selectValueList.getItemCount( ) > 0 )
			{
				selectValueList.select( 0 );
				getOkButton( ).setEnabled( true );
			}
		}
		catch ( Exception e )
		{
			ExceptionHandler.handle( e );
		}
	}
}