During the creation of a SG Project the name was set in UPPER case: TEST This was an error so it was then edited to lower case: test Now I visualize it correctly in SG [image] The issue is that in the before_app_launch I define the context like so: project_path=tk.project_path tk.context_from_p…

Adding to this … here the issue again: [image] Any Idea?

I’ve even tried to set the Project Name through API shotgun.update("Project", 188, {"name": "test"}) And still the issue persists. Is there any cached data I should “flush”?

Have a look at the tank_name property, which corresponds to the name used for directories, etc.

[image] mmoshev: tank_name property Not sure what you mean … [image] tank_name is a field of my project entity and I don’t see how it can affect the name field which, as you can see from the prior grabs , differs in case if I query it with the shotgun.find command or the context_from_path co…

Project Name Case cached?

Pipeline Integrations

lozo_lbx April 18, 2023, 12:21pm 4

Another strange thing is that this seems to be related only to the Primary config!

Topic		Replies	Views
Project name folder to be different from registered Pipeline Integrations	1	231	December 22, 2022
Change a Project folder name after Advanced Project Setup Pipeline Integrations	1	394	June 29, 2022
Am I able to change the project's "tank_name" after the project has been created? Pipeline Integrations	1	89	August 19, 2025
Add "project.tank_name" and "step.short_name" to sgtk.Context Pipeline Integrations	8	1424	April 1, 2021
Get Project name in configuration yaml Pipeline Integrations	2	414	November 2, 2022

Project Name Case cached?

Related topics