Known Limitations in Nakisa Lease Accounting Suite

The following table lists the known limitations for Nakisa Lease Accounting Suite that may be considered in future major and minor releases. (Note that patch releases deliver bug fixes only, and are not considered to be minor releases.)

Reference Number	Description
LEO 35	For short term or low value lease types, when users view the All Columns schedule, they are not able to export that view to Excel. As a work around, users can export the schedule via the Mass Export feature.
LLT 25	Currently, the Modification Date of a second indexation event cannot be on the same day as the Indexation Date of a previous indexation event. The user must select the day after the last Indexation Date, or revert the indexation event for each affected activation group.
NFS-16077	If an Administrator configures an application-level Default Field Value that is locked (i.e., users cannot edit this field manually), users can still set the field to a different value in the Mass Import Excel template and successfully create the object with the different value. To workaround this issue, review the configured Default Field Values for any locked application-level configuration, and align your Mass Import Excel with them.

Reference Number

Description

LEO 35

For short term or low value lease types, when users view the All Columns schedule, they are not able to export that view to Excel. As a work around, users can export the schedule via the Mass Export feature.

LLT 25

Currently, the Modification Date of a second indexation event cannot be on the same day as the Indexation Date of a previous indexation event. The user must select the day after the last Indexation Date, or revert the indexation event for each affected activation group.

NFS-16077

If an Administrator configures an application-level Default Field Value that is locked (i.e., users cannot edit this field manually), users can still set the field to a different value in the Mass Import Excel template and successfully create the object with the different value.

To workaround this issue, review the configured Default Field Values for any locked application-level configuration, and align your Mass Import Excel with them.