topic Re: Current Workspace for Parameters in Model Builder in ArcGIS Pro Questions

Current Workspace for Parameters in Model Builder

EuropaxEarth — Fri, 21 Jul 2023 17:01:36 GMT

Hello,

I have created a model that clips DEM data to my selected parcel boundary to output "Contours_Layer" and "Slope_Symbolized". I have them set as parameters.

This model will ultimately be used in different projects. The goal would be to use the model without having to manually type in the file paths of the current project I am in.

Is it possible to set the file path for "Contours_Layers" and "Slope_Symbolized" to the current geodatabase?

I tried using "default.gdb" "%CurrentWorkspace%\" but recived the following error message: 000875: <value>: <value>'s workspace is an invalid output workspace.

What is the correct way to set the output of my parameters to the current workspace?

I believe in arcpy the proper syntax is as follows:

import arcpy aprx = arcpy.mp.ArcGISProject("CURRENT")

Unless I were to add a script into the model, I doubt the syntax above is the same for model builder.

Thank you in advance!

Re: Current Workspace for Parameters in Model Builder

BryanJohnstone — Wed, 07 May 2025 00:13:41 GMT

Wondering if you ever found a solution to this as I am experiencing a similar issue...

From my investigations, you might need to use %workspace%\Contours_Layer & %workspace%\Slope_Symbolized

%workspace% should reference the current default gdb.

My issue is that when I create my model, package it up in a toolbox and then into a Project Template (.aptx) for other users to access...the %workspace% in the output parameter of my model is changed to a temp location in the AppData folder...

Cant figure out how to just have the model retain the %workspace% shortcut so that it always just outputs to the current gdb given that users are accessing this all through a .aptx template.

Re: Current Workspace for Parameters in Model Builder

MetralAlexis — Thu, 07 May 2026 14:59:59 GMT

I had the same issue. Finally, I zipped the project instead of creating a package. Once unzipped by the end-user, it keeps the %workspace% instead of replacing it by the temp path related to the person who developed the project.