Default folder for project creation not applied to PROJECT_CREATOR macros.

Diogo

Created a project creation macro (macroRoles: [{"type": "PROJECT_CREATOR"}]) that when is invoked from the central "New Project" entry point, in the DSS home page, does not appear to respect the instance's configured 'Default folders for project creation' rule (Administration → Settings → Themes & Customization), even though the native project creation types, like blank project and import, do.

Current behaviour has the _projectFolderId parameter being set as empty, which seems to signify root directory, and before even entering the plugins execution thread, the process fails as users in my org are barred from creating projects in root folder.

My question is - How can this variable be overridden or checks be skipped, so users can call this from whichever folder and do so without their permissions being elevated?

Dataiku version used: 14.1.1

ThomasW

Hello Diogo,
Thanks for raising this. This issue is fixed in the incoming DSS 14.7.4 release.

Project creation macros now use the same folder-selection rules as manual project creation:

• Create in the current non-root project folder if the user can write there.
• Otherwise, use the configured default project folder defined in the admin settings.
• From the home-page entry point, if no default folder applies, DSS uses root, so the user needs the May write in root project folder permission.

DSS still verifies that the user can write in the resolved folder; no additional permissions are granted.

Have a nice day,
Thomas