Summary
Select the release feature from the table below to be taken directly to that section of the release note.
| Defect 1 | Defect 2 |
|
GetDriversByInternal Not Populating Driver Amount for Sales GetDriversByInternal API call was not correctly returning driver amounts for the "SALES" volume type, causing users to see a value of 0. |
Resolved defect where duplicate ASC user accounts were bein created due to a case sensitivity issue with HR Ids.
|
Release date for all features: January 9th, 2025
GetDriversByInternal Not Populating Driver Amount for Sales
Description
The GetDriversByInternal API was not correctly returning driver amounts for the "SALES" volume type, resulting in users receiving a value of 0 for driver amounts when pulling data for SALES volumes.
Resolution
The defect has been fixed, and the GetDriversByInternal API now correctly includes driver amounts for "Sales" volume type. Users will receive accurate data when querying this volume type.
Customers Affected
All customers using the GetDriverByInternal API to retrieve driver data for SALES volume type.
HS I Duplicate ASC accounts
Description
A defect was identified where duplicate ASC user accounts were being created due to a case sensitivity issue with HR IDs. When users were imported via FTP or API, the system failed to recognize HR IDs with case differences, leading to duplicate accounts.
Resolution
The defect has been resolved to ensure HR ID case sensitivity no longer results in duplicate account creation. The fix has been applied and thoroughly tested, confirming functionality across all clients. The system now accurately identifies existing users regardless of case changes in HR IDs.
Customers Affected
This fix applies to all clients using the ASC import functionality, addressing duplicate account creation issues.
Comments
Please sign in to leave a comment.