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/data/ui/property/AbstractPropertyDialog.java
{
		switch ( buttonId )
		{
			case IDialogConstants.OK_ID :
			{
				okPressed( );
				break;
			}
			case IDialogConstants.CANCEL_ID :
			{
				cancelPressed( );
				break;
			}
			case IDialogConstants.HELP_ID :
			{
				performHelp( );
				break;
			}
			default :
			{
				super.buttonPressed( buttonId );
			}
		}
	}
	/**
	 * Called when the user pressed the Ok button. It is called only if all the
	 * pages return true for their individual
	 * {@link org.eclipse.birt.report.designer.data.ui.property.IPropertyPage#performOk() performOk}
	 * methods. Derived classes can save the contents of the dialog and perform
	 * any validation if necessary on the contents. <br/>The dialog is closed if