RESOLVED IN 4.2.0.0: error saving workorder manually generated from PM via a dataportal connection

The following occurs in such a situation:
User is connecting via a dataportal connection
User manually generates a workorder from a PM
User selects Save or Save & Exit in the newly generated workorder, and error occurs similar to below (number varies as dependant on internal GUID)
If using Firebird:

violation of PRIMARY or UNIQUE KEY constraint “PK__AWORKORDER__587208C1” on table “AWORKORDER”

Or error may be similar to if using SQL:

Violation of PRIMARY KEY constraint ‘PK__AWORKORDER__114A936A’. Cannot insert duplicate key in object ‘dbo.aWorkorder’

What is occurring with the dataportal connection is that the workorder is actually created with a new workorder number - so when the user tries to save, a conflict occurs (already have a workorder with that same number).

If instead the user does the following, they can than go back into the generated workorder and enter additional details etc as needed.

User is connecting via a dataportal connection
User manually generates a workorder from a PM
User before entering any additional details, selects the X in the upper right-hand corner to close out
User selects “No” to the question “Do you want to save changes?”
The user now views the Service Workorder grid, and Refreshes
The user now sees the newly created workorder and can now open its entry screen and enter any additional details as desired.
Development will be addressing this dataportal issue in a maintenance update.

[FORUM NOTE: This issue has been addressed in AyaNova 4.2.0.0]