| Previously, you could not modify WorkOrderHeaderCost file name using the Transform_WorkOrderHeaderCost job because the services associated with the job did not support customization. This issue has been resolved. | US434020 |
| Previously, the data loader logs were stored as long text in the Interface Log records. This resulted in increased size of the records, which degraded the performance of Predix Essentials. This issue has been resolved. | US431006 |
| Previously, you could not create an inspection task if you did not have the license for SAP Work Management Interface even though the license was not required to create the task. This issue has been resolved. | DE139956 |
| Previously, using the global search, when you attempted to search for a record associated with the Taxonomy families, an error occurred, and no results were returned. This issue has been resolved. | DE139330 |
| Previously, when using the APM Family Data Loader to import data, if the Site Reference Name column of the Data worksheet did not contain the Family ID, the data load was successful, however, the relationship was not created. This issue has been resolved. Now, in this scenario, the relationship is created, and a warning message is written to the interface log. | DE138511 |
| Previously, when you attempted to load Production Loss Analysis (PLA) data loaders through the Automatic Data Loader, an error occurred. This issue has been resolved. | DE138256 |
| Previously, when loading data using the Unified Asset Ingestion Data Loader, the non-English characters in the data were converted to ‘?’ in the Predix database. This issue has been resolved. | DE137904 |
| Previously, when you extracted SAP characteristics to create Technical Characteristic records in Predix Essentials, single-value date and time characteristic values were not populated. This issue has been resolved. | DE136026 |
| Previously, when uploading records using the Unified Asset Ingestion data loader, the data was uploaded to the Meridium database, even if the upload failed in the Predix database. This resulted in the Meridium and Predix databases being out of sync. This issue has been resolved. | DE135978 |
| Previously, in the APM Family data loader, if you specified a unit of measure (UOM) behavior for a given field, and you loaded that data into Predix Essentials, and then, if you updated the UOM value and reloaded the data, the field value in Predix Essentials was not converted as per the updated UOM. This issue has been resolved. | DE135246 |
| Previously, if the Data Loader Configuration family contained a record with the Loader ID only, when you clicked the Import New button in the Data Loader window, an error occurred. This issue has been resolved. | DE133385 |
| Previously, when loading data using the Unified Asset Ingestion Data Loader or the APM Family Data Loader, if there was an exception in the Configuration worksheet, the error log did not record the issues clearly. This issue has been resolved. Now, the error log contains detailed information about the issues encountered, the causes of the issues, and recommendations on how to fix the issues. | DE129508 |
| Previously, in the APM Family data loader, if you prefaced a Field ID with the Family ID, and if there was a corresponding behavior field indicating the Unit of Measure (UOM) or time zone for that field, and the behavior field was not prefaced with the Family ID, the UOM or time zone behavior was ignored. So, the field value was not converted to the corresponding UOM or time zone in Predix Essentials. This issue has been resolved. | DE128483 |
| Previously, when loading data using a data loader, if the data loader input file name contained special characters that the APM Connect File Share system did not handle, an error occurred. This issue has been resolved. | DE127324 |
| Previously, when using the APM Family Data Loader to load data to a Family whose Family ID contained at least one space, and a column on the Data worksheet was prefaced with that Family ID, the upload failed. This issue has been resolved. | DE125932 |
| Previously, when attempting to write the Interface Record Log Text, there were many System.OutofMemory exceptions due to the large size of the Log Text file. This issue has been resolved. Now, the size of the Log Text file is capped at 256 MB. | DE123757 |
| Previously, when you attempted to load records through the APM Family Data Loader, if a field contained the string value "False", an error occurred, even though "False" was a valid value for that field. This issue has been resolved. | DE120260 |