Version 9.1.164.1 (Support Release - 3 June 2025)

Performance Management 
 Path to link Signify to Power BI (#132335) 
 Problem 
 
 An additional api required to export all user contract data for a review year and review setup 
 
   
 Solution 
 
 Create a copy of rpc ListReviewYearSetupUserContracts (ListReviewYearSetupUserContractsRequest) returns (ListReviewYearSetupUserContractsResponse); and extend to include all users 
 Include location in org 
 Remove image path for performance 
 
   
 
 Imports 
 PaySpace Signify discrepancy script (#129254) 
 Problem 
 
 When data is not staged in the user stagings for an import, then the exported Excel sheet is broken without data. 
 Data fields are inconsistent in the export 
 
   
 Solution 
 
 Add a check to export a default error 
 Add a caste to shortdatestring for datetime and datetime? fields 
 
   
 PaySpace (#132260) 
 Problem 
 
 When the Payspace client does not grant access to the OrganizationPositionDetail, then the following API call fails as forbidden 
 string url = $"{connector.BaseUrl}/v1.1/{companyId}/OrganizationPositionDetail?$count=true"; 
 
   
 Solution 
 
 Add try catches when pulling data for the OFO code to suppress and log the failure should it occur, and then continue with the import 
 
 
 Imports 
 Issue when importing data in another root than IN01 (#132815/132240) 
 Problem 
 
 When providing other data in the import for org level 1 than the default IN01 data, the import fails with the error: The org node to link the user's position to could not be found." 
 
   
 Solution 
 
 Add org level 1 as received data, and fall back to the default only when no data is provided