Why are there known product issues?
Sparkrock personnel work hard to prevent product issues from reaching customers, and to resolve issues in a timely fashion when they are discovered. However, there are times when there may necessarily be a lag between discovery of an issue and a resolution. In such cases we will list significant pending issues here. Workarounds and/or potential resolutions are provided on an item by item basis, as available.
|CAS-13456-P5Q0||(Release 9.06 and 9.06 SP1) When running the EWA Load Standard Page Setup routine, two legacy web services (AEP User Delegates and AEP Profile Card) are loaded and need to be manually removed.|
|4013||Incorrect results can occur when the Employee Center SharePoint server and Microsoft Dynamics NAV server are set to different time zones. Work with your IT team to ensure that the two server time zones match.|
|3969||In Purchasing and Expenses, an error is generated when trying to calculate Quantity * Unit Cost when the result exceeds the system maximum size (technically, the size of Int32). This condition will not occur in normal use of the solution.|
|4432||When working in Purchase Request lines, the combination code is not being cleared. This makes the line invalid if the value in the combination code and defaulted G/L account is different.|
|4452||When working with approvals, adding or updating expense line changes the Alternate Manager to original value. This is an artifact of the way that approvers are calculated in Employee Center. Alternate Approvers should be set after all lines are completed.|
|4465||Changing an expense type from "Location to Location" to a basic type may result in a negative quantity appearing. If this happens delete the line and then add it back as the basic type.|
|When saving POs where an expense line has been updated, including a change to the expense type or dimensions, Employee Center can return an error message about a "parameterized query". The work around is to delete the line and recreate it.
Applies to 9.06 SP1 and prior releases, resolved by 9.04 Service Pack 2. Please Contact Sparkrock support if you need this fix in a different version.