Latest Contributions by TimOrmsby

Benjamin, see this thread for some background information that may be useful: Check in ArcGIS Pro license-named user. ... View more

John, are you also checking in the license with the same username/password that you used to check out the license? Same machine and same sign-in credentials? ... View more

And one more link to add to Dan's: Start ArcGIS Pro with a Named User license—ArcGIS Pro | ArcGIS Desktop: see the last section of the topic. When you try to check in the license, are you signed in with the same account that checked out the license?  ... View more

Dan, the topic Release notes for ArcGIS Pro 2.2 includes issues addressed at ArcGIS Pro 2.2.1 at the top. ... View more

Michael, I don't think the command toggles off (which might be a nice enhancement). I think you have to go to the List By Selection tab on the Contents pane, mentioned by John, above, and set selectability for the layers you want. ... View more

You're right about the redundancy of steps 17, 18. One of those two steps should come out. (It doesn't matter if you select Model_output.gdb from Folders or from Databases--they're pointing at the same item.) I'll submit a doc bug, but it's likely too late to get fixed in the upcoming release. Note: I see that this problem has already been identified and fixed in the prerelease doc. It will appear in the next software/doc release. Confirming your edit 2 on the output grouped table name... you have to specify a file name for the table, not the geodatabase name. I've worked through the tutorial a couple of times since your original post and haven't been able to repro your results except when I fail to save the model properties (step 21) after setting the scratch workspace. If you try it again and still get the same result, please message me and we'll try to get the gp team to look at it. ... View more

Jayanta Poddar is right. In the tutorial, under Open the project, step 2, you need to click Open an existing project or Open another project (first bullet point in Jayanta's response). See also image below. Your screen shot shows you are trying to create a new project when you want to open an existing project. ... View more

Hi Robert, there's something going on I don't really understand. I'll ask some people on the geoprocessing team if they can look into it. The path you show to the Model_output geodatabase: C:\Users\rghall\Documents\ArcGIS\Packages\Make_a_model\Model_output.gdb isn't the path you should get. Following steps 11-13 in the section Set model properties and environments, the new geodatabase should be created inside the project package folder. In other words, your path should look like: C:\Users\rghall\Documents\ArcGIS\Packages\Make_a_geoprocessing_model_D2D7AC16-48C3-4826-ADE1-5332A4C4EA0CF\Model_output.gdb. The fact that your path points to \Make_a_model\ instead of the package folder makes it seem like you might have typed in part of the path name, rather than browsing to it, when you created the file geodatabase. Is that possible? I can reproduce your results if I create a new file geodatabase and, in the New File Geodatabase dialog, browse to C:\Users\<userprofile>\Documents\ArcGIS\Packages and at that level type \Make_a_model\Model_output as the name of the geodatabase. In that case, the geodatabase will show up in the Catalog pane and can be set as the scratch workspace. However, when you run the tool and enter an output feature class, the output path points to the original project geodatabase--exactly as you show. By clicking the Browse button next to the output feature class, you can point the output to the new file geodatabase (the one you want)--but of course that defeats the point of setting the scratch workspace. Like I said, I don't know what's going wrong... something to do with the structure of project packages? I'll see what I can find out. In the meantime, try retracing your steps in the exercise and creating the Model_output geodatabase within the project package folder--as shown in the image after step 13. In that case, the rest of the steps should work properly. NOTE: After doing some more testing, I think the problem may be something simple. After you set the scratch workspace to the new model_output geodatabase, you have to save the model. (This is step 21 in the relevant section of the tutorial.) If you don't do this save, you see the behavior you describe: the path to the new geodatabase is shown in the Environment settings, but when you run the tool, the output defaults to the original project geodatabase. Basically, the model needs to be saved before the new scratch environment is recognized. Can you try this and see if it resolves the issue? If so, I think it's probably expected behavior. And then disregard everything above about the location of the output geodatabase, which now seems irrelevant. ... View more

Robert, what version of Pro are you running? Asking because I haven't been able to repro the problem on 2.1 or 2.2 beta software. If you're using something older, I'll give that a try. ... View more

Yes, please add to the ArcGIS Ideas page. Also, fyi your observations have been passed to the Pro development team that works on this. ... View more

Hi, yes, Pro documentation team has seen this thread. Thanks for reporting the confusion. ... View more