ID 405395 - NodegraphAPI.GetOriginalSourceFile() and NodegraphAPI.GetOriginalProjectAssetID() may return a potentially incorrect all lower-cased project filename and asset ID

Follow

Problem summary:
NodegraphAPI.GetOriginalSourceFile() and NodegraphAPI.GetOriginalProjectAssetID() may return a potentially incorrect all lower-cased project filename and asset ID.

The bug occurs after opening a project or after reverting an opened project, then running NodegraphAPI.GetOriginalSourceFile() or NodegraphAPI.GetOriginalProjectAssetID().
The bug does not occur after saving the project and running NodegraphAPI.GetOriginalSourceFile() or NodegraphAPI.GetOriginalProjectAssetID().

Customer reported version:
Katana 3.2v1

Steps to reproduce:
  1. Start Katana
  2. Save the project with capitalized letters (File > Save or Ctrl+S).
  3. Revert the project by choosing File > Revert in Katana's main menu bar.
  4. Run NodegraphAPI.GetOriginalSourceFile() or NodegraphAPI.GetOriginalProjectAssetID() in the Python tab.
Expected behavior:
NodegraphAPI.GetOriginalSourceFile() returns the project filename with correct capitalization.
NodegraphAPI.GetOriginalProjectAssetID() returns the asset ID with correct capitalization.

Actual behavior:
NodegraphAPI.GetOriginalSourceFile() returns the project filename with lower-case characters.
NodegraphAPI.GetOriginalProjectAssetID() returns the asset ID with lower-case characters.

Workaround:
There's no known workaround to get the original filename the project was last saved to with correct capitalization.
However, NodegraphAPI.GetSourceFile() can be used instead to get the filename where the current project was loaded from.

Reproduced by support:
This bug has been reproduced in:
Katana 3.2v1 - CentOS 7, Windows 10
Katana 3.1v5 - CentOS 7, Windows 10
Katana 3.0v1 - CentOS 7, Windows 10
Katana 2.5v1 - CentOS 7, Windows 10
Katana 1.6v3 - CentOS 7

Earliest version tested:
Katana 1.6v3 - This issue appears to be in all versions of the product
 

    We're sorry to hear that

    Please tell us why