You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additionally, when I attempt to "Add" the cube through the source control menu in the Architect page, I get the message:
Did not find a matching mapping for "{{Cube name}}.CLS". Skipping export.
It looks like Embedded Git is getting the name of the cube from the UI rather than the full class, so when it attempts to export the class, it cannot. Not sure if this is an Embedded Git issue (not correctly resolving the class name) or an Iris issue (passing in the wrong value to the Source Control hooks).
It looks like this is the code flow:
AddToSourceControl()
ExportItem()
FullExternalName()
When the following method calls return MappingExists=0, prints out the above message and quits without exporting the class.
ExternalName()
Name():
Determines MappingExists = 0 (which makes sense because the cube name is just free text and would not match any of the package patterns we have configured for Embedded Git)
Just concatenates the incorrect class name with the (correct) git directory and returns
$zv: Iris for Windows (x86-64) 2025.1.2 (Build 374U)
Work Around: When I open the class in VS Code, and use the source control menu to add it, that works. (Embedded git is passed the correct value for the class). I would hazard a guess that if I put the full class name as the cube name, the export would work.
Did not find a matching mapping for "{{Cube name}}.CLS". Skipping export.
This is an IRIS issue which is fixed in 2026.1.0, internal reference DP-446572. I will consult with @isc-egabhart to see if we can work around it in the source control extension.
Activity
cambot commentedon Aug 19, 2026
Additionally, when I attempt to "Add" the cube through the source control menu in the Architect page, I get the message:
It looks like Embedded Git is getting the name of the cube from the UI rather than the full class, so when it attempts to export the class, it cannot. Not sure if this is an Embedded Git issue (not correctly resolving the class name) or an Iris issue (passing in the wrong value to the Source Control hooks).
It looks like this is the code flow:
AddToSourceControl()ExportItem()FullExternalName()MappingExists=0, prints out the above message and quits without exporting the class.ExternalName()Name():MappingExists = 0(which makes sense because the cube name is just free text and would not match any of the package patterns we have configured for Embedded Git)$zv: Iris for Windows (x86-64) 2025.1.2 (Build 374U)Work Around: When I open the class in VS Code, and use the source control menu to add it, that works. (Embedded git is passed the correct value for the class). I would hazard a guess that if I put the full class name as the cube name, the export would work.
isc-pbarton commentedon Aug 19, 2026
This is an IRIS issue which is fixed in 2026.1.0, internal reference DP-446572. I will consult with @isc-egabhart to see if we can work around it in the source control extension.
This is going to be an Embedded Git issue. I will look into a fix