AVEVA Production Management 9​.2​.0 release notes

3986524

Saving a project takes too long after the service runs for several hours

Each Inventory movement event submission acquires a project save handler. Due to memory leak, the handler is not disposed after submission. As more events are submitted, more handlers leak. During project save, these unnecessary handlers execute and cause delays. To resolve the issue, we have fixed the project save event handler memory leak.

3694127

Document item validation error due to spaces in the path name

When you configure the Document Item with a URL or a path name that contains spaces, Studio shows a validation error. However, it opens correctly in Production Analyst. To resolve this issue, this update validates the file path, allowing spaces in the path name.

3682950

Unable to rename Shared favorites folders if the parent isn't the root

Renaming a Shared favorites folder that isn't the root fails to update the UI because the client sends the full name with tab-separated values, which don't match the database. To resolve this, we modified the process to send only the folder name, ensuring the update persists.

3633067

Record creation delayed after upgrading to version 9.0.0

After upgrading to version 9.0.0, record creation is delayed. We resolved this by improving multi-threaded stream performance when using a local state database.

3613869

.NET Framework error occurs when running CLR procedure with TLS 1.0 and 1.1 disabled

In Production Management 9.1.0, running a CLR stored procedure after configuring the WCF binding fails with a .NET Framework exception because TLS 1.0 and 1.1 are disabled, blocking client-server communication. We have resolved this issue by switching to TLS 1.2 or 1.3.

3461527

When a logged-in user belongs to multiple AD groups configured in Production Management, the auto-refresh calculation considers the setting from a group where auto-refresh is disabled instead of the minimum interval

To resolve this issue, the auto-refresh calculation now considers the minimum interval for multiple user groups and ignores the user group with auto-refresh disabled.

3455503

Production Analyst clipped duration conversion causes a precision issue

The duration display formatter in Production Analyst converts the time value from a double to a long, causing a precision issue. This is resolved by using the converter from the latest .NET libraries.

3426749

The AVEVA Production Management project encountered a SQL arithmetic overflow error after an upgrade

After upgrading AVEVA Product Management, the project encountered a SQL exception: arithmetic overflow error converting identity to the int data type. To resolve this, we added a script to check and convert the SampleId column in the SampleStore table to bigint.

3410674

Adding new variables breaks the offset settings for other variables in the AVEVA Historian group folder

Adding new variables to the AVEVA Historian group folder breaks the offset settings of other variables. This is due to an existing issue (CE-2229) where the new variables capture samples from the start of the cache duration, leading to performance issues. We resolved both issues by enhancing the code to adjust the offset time for existing variables when adding new ones.

3324810

'Last Day or Current Day' filter doesn't work properly in Inventory 'Balance Over Time' view

When the 'Last Day or Current Day' filter is applied to the sample period in the Inventory 'Balance Over Time' view, it shows all balances instead of balance for today and yesterday. We resolved this by updating the code to return the correct balances.

KI-41

SQL errors for projects containing large quantities of custom fields

There is record-size limit of 8,018 bytes for tables that use sparse columns. When the converted data plus existing record data exceeds 8,018 bytes, MSSQLSERVER ERROR 576 is returned. When columns are converted between sparse and non-sparse types, the Database Engine keeps a copy of the current record data. This temporarily doubles the storage that is required for the record.

Workaround

None

KI-40

SQL errors for projects containing large quantities of custom fields

There is record-size limit of 8,018 bytes for tables that use sparse columns. When the converted data plus existing record data exceeds 8,018 bytes, MSSQLSERVER ERROR 576 is returned. When columns are converted between sparse and non-sparse types, the Database Engine keeps a copy of the current record data. This temporarily doubles the storage that is required for the record.

Workaround

None

KI-39

Updating records while auto refresh enabled may result in incorrect data

If a user has auto refresh enabled and tries to edit a record as a refresh is in progress, the changes may be incorrectly applied to the first record instead of the users initial selection.

Workaround

Pause auto refresh via the toolbar (under the refresh icon), make the required changes, then re-enable auto refresh.

KI-38

Charts panel displays “No Data Available” when viewing a Shared Favorite created by another user

When a user creates a Shared Favorite and shares with other users, the other users cannot view the charts on the shared views. Only data shows, and the charts panel displays “No Data Available”. This is due to favorites being associated with the regional settings of each user. Favorites are specific to a regional setting. For example, if a favorite is created on a system where regional setting for decimal is "." (period) - The same cannot be used in a system where regional setting for decimal is "," (comma).

Workaround

Create separate Shared Favorites for every regional setting.

KI-37

Unable to filter on field values that contain multiple consecutive spaces

Fields that contain values with multiple consecutive spaces fail to return results when filtered on.

Workaround

Use * in the filter when multiple spaces are required.

KI-36

Evaluated fields shown to 14 decimal place precision with trailing zeros

Evaluated fields are sometimes shown to 14 decimal places when not required for the field value.

Workaround

Apply a display format to the field. If a display format is specified, the field will adhere to specified display format.

KI-35

Database2AmplaIntegration with Sample Period as filter will potentially not find the matching record even if one exists, when date times up to milliseconds precision is used.

If submit data web service is used to insert records to a Process Quality Reporting point, with Sample Period that includes milliseconds, the record is persisted with milliseconds.

For example:

<Field>

<Name>Sample Period</Name>

<Value>2016-03-15T08:10:20.30Z</Value>

</Field>

When a Database2AmplaIntegration is used to update the above record with the Sample Period field used as a filter, the milliseconds used in the integration item, is not used in the query. Therefore, the query does not return the matching record (the one inserted by the web service).

Integration select query:

select '2016-03-15 18:10:20.3000000' AS SampleDateTime, 111 AS A, 222 AS B

Workaround

Remove milliseconds from the datetime field on insert.

KI-33

When a material class constraint does not match the DestinationMaterialClassExpression value, no error is returned by reprocessing

When moving a material lot between equipment, if the expected destination material class does not match the material class constraint of the work center, Ampla does not produce a processing error, although it should.

Workaround

Ensure during configuration that the material class of a material lot and the destination work center are matching.

KI-31

A menu option for Select Period Beginning drop-down menu does not display

In some cases, a menu item that should appear in the Select Period Beginning drop-down menu will not display. This issue occurs on the Filter on Sample Period dialog box, which is invoked by clicking Sample Period on the Filter Builder. On the Filter by Sample Period dialog box, select 'Month Beginning' for the Specific Period. Additional options appear for selecting Year and Period Beginning. When you click the drop-down menu for Period Beginning options, you see a list of periods. These are user-configured values and are usually months. This issue relates to missing values from the list of selectable options. This can happen for one of two reasons:

1. Blackout periods. Blackout periods with a conflict with a period can result in the period not appearing. If a month has a blackout period with a reference time that matches a reference time of a menu item, then that item will not appear in the month selector.

   For example, a Blackout Period has a reference time of 6/1/2018 12:00:00 AM. The month of June also has a reference time of 6/1/2018 12:00:00 AM. This conflict causes June not to appear in the drop-down list.

2. Overlapping periods. If the reference times of periods overlap, this conflict can also cause a menu item to not appear in the list.

Workaround

Manually edit the month value that appears under Sample Period on the Filter Records dialog box to be within the required period.

Try one of the following workarounds:

• Ensure blackout period reference times don't match period reference times.

• Ensure periods do not have overlapping period reference times.

• Manually edit the month value that appears under Sample Period on the Filter Records dialog box.

KI-30

Wonderware Online Insight does not validate the endpoint when uploading metadata and can return a false positive success message

If a different Wonderware Online Insight endpoint is specified to the correct one for the solution (For example, UK endpoint instead of Australian endpoint) when a user tries to upload the metadata to the endpoint they still receive a "Metadata uploaded successfully" message, even though upload was not successful.

Workaround

Verify that you are using the correct endpoint for the solution.

KI-28

Changes to metadata values for WonderWare InSight Integrations are not saved

Wonderware Insight does not support editing the values for some of the metadata fields (such as data type, min and max values) if the metadata has previously been published to Wonderware Insight.

Workaround

None

KI-27

Possible port conflicts with RabbitMQ

When you install Rabbit MQ for Service Bus integrations, be mindful of existing port conflicts. If you have ActiveMQ already installed and try to enable protocols that are common to both RabbitMQ and ActiveMQ, there could be port conflicts. The default port that Ampla uses for RabbitMQ does not have a conflict with the default ActiveMQ port. However, enabling AMQP, STOMP, MQTT in RabbitMQ would result in a conflict.

Workaround

Check that the services are not using conflicting ports.

KI-26

Cause Location in the Navigation Hierarchy of Production Analyst does not change to Location when the module changes

If a user selects Cause Location from the Navigation Hierarchy menu while in the Downtime module standard view then navigates to a different module, the Downtime data continues to be displayed and is editable in the grid.

Workaround

Changing the Navigation Hierarchy value to Location fixes the views.

KI-25

Cannot edit any movement event field that has been captured under a Movement item, when using SourceMaterialClassExpression or DestinationMaterialClassExpression.

If you use SourceMaterialClassExpression or DestinationMaterialClassExpression on a movement item that has a capture condition, a Material Class Constraint must also be configured. If you do not use a Material Class Constraint, you will not be able to edit movement event fields under this item.

Workaround

Configure a Material Class Constraint on a Movement item, if you use a Material Class Expression.

KI-18

Unable to filter by Location Identifier in Knowledge and Maintenance modules

A current limitation in the Knowledge and Maintenance modules is that Production Analyst does not support the ability to filter by Location Identifier, even when the Location Identifier field property Filterable is set to True.

Workaround

No current work around.

KI-17

Planning grid updates need a refresh, before changes can be made from the Gantt chart

In Ampla Planning, changes to the Planning view grid are lost if more changes are done through chart without refreshing the grid first.

Workaround

If you make changes in the Planning grid, refresh the grid to save these changes before modifying data through the Gantt chart.

KI-15

Metrics schedulerActivationObservable causing service shutdown delay

When verbose logging is turned on, the Metrics schedulerActivationObservable makes a high number of calls, which can cause delay in Ampla service shutdown.

Workaround

No workaround.

KI-11

Wonderware Connector does not support data backfill functionality

Ampla does not yet support the ability of the Wonderware Historican two-tier architecture to support redundant connectors and backfill data after a connector disruption.

Workaround

No current workaround.

KI-10

Validation for Activity ID duplicate values occurs only within same equipment item

It is possible to have the same Activity ID value under more than one Planning reporting point. However, this is not desirable because it causes issues when trying to link a child plan to a parent plan via the parent Activity ID if the values are not unique.

Workaround

Avoid duplicate values wherever possible. Use unique Activity ID values throughout the project.

KI-7

Movements that are inserted via web service do not get processed immediately

When movements and quality records are in the same SubmitData web services request, in some circumstances, the movements will not be processed immediately.

Workaround

Execute the Reprocessing action, or submit movements and quality records in separate web service requests.

KI-4

DestinationQuantity on movements should not be editable

When the DestinationQuantityMode property for a material movement is set to Conversion, the DestinationQuantity is currently editable; however, it should not be editable.

Workaround

No current workaround.

KI-3

Chart properties not translated into all languages

There is an issue with translations for names of Chart properties in Production Analyst. Chart properties will still appear in English for some language selections.

Workaround

No current workaround.