Initializing help system before first use

# xpressinsight.AppInterface.rename_scen_attach

Purpose
Renames an existing scenario attachment.
Synopsis
`xpressinsight.AppInterface.rename_scen_attach(self, old_name: str, new_name: str) -> None`
Arguments

old_name | The existing filename of the attachment to be renamed
new_name | The new filename of the attachment. Must not already be used for a scenario attachment.

Return value

This function may raise the following errors:

AttachNotFoundError

  If the specified attachment was not found on the scenario.

AttachFilenameInvalidError

  If the given new attachment name was invalid

AttachAlreadyExistsError

  If the given new attachment name is already in use

AttachError

  If there is some other error renaming the attachmnet.

Example
Example of renaming an existing attachment of the current scenario from my_attach.dat to my_attach-2015.dat.

    >>> insight.rename_scen_attach('my_attach.dat', 'my_attach-2015.dat')

Further information
1. The method rename_scen_attach is part of the class xpressinsight.AppInterface.
2. To maintain backwards compatibility, attachment operations will only raise exceptions on error if the raise_attach_exceptions attribute of either the AppConfig or AppInterface class is set to True. When this is not the case, after every call to this method you should check the value of insight.attach_status to see if your request succeeded.
3. The attachment will not be renamed on the Insight server until the scenario completes.
4. Attempting to access attachments outside an Xpress Insight scenario will access local files that have been supplied to this class.
Related topics
AppInterface.attach_status
Parent Topic App Interface Classes

© 2001-2026 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.