Saving Maps through Jtx 931

3331
2
Jump to solution
03-08-2011 04:21 AM
by Anonymous User
Not applicable
Original User: patrick.murphy

I manage a group of analysts that all have different methodologies on extraction. They use different layers, color things differently, etc. Some of the users are allowed to save their map comps through jtx, while others are not. This is an issue that isn't completely disrupting production, but it is slightly impacting the speed of production for others as they have to manually add the same layers everyday or every time they close the job created from JTX.
0 Kudos
1 Solution

Accepted Solutions
by Anonymous User
Not applicable
Original User: topeb

Hi Patrick,

If you are still having this issue with the maps here is a suggestion.

You can use a combination of extended properties and the "open Alternative mxd" option on the launch ArcMap step.
The alternative MXD location can be a file path on disk, that is set by your GIS analysts through the extended properties field. This field will be the value you define the step with [JOBEX:FieldstoringFilePath]. At runtime this token will be replaced with the file path that your analysts provide there.

Thanks,
Tope

View solution in original post

0 Kudos
2 Replies
by Anonymous User
Not applicable
Original User: topeb

Hi Patrick,

If you are still having this issue with the maps here is a suggestion.

You can use a combination of extended properties and the "open Alternative mxd" option on the launch ArcMap step.
The alternative MXD location can be a file path on disk, that is set by your GIS analysts through the extended properties field. This field will be the value you define the step with [JOBEX:FieldstoringFilePath]. At runtime this token will be replaced with the file path that your analysts provide there.

Thanks,
Tope
0 Kudos
by Anonymous User
Not applicable
Original User: patrick.murphy

Thanks! We have currently had to relocate our operations and are still "standing up" our working environment. I will definely refer back to this post should the problem resurface when we are again operational. Thank you for your suggestion
0 Kudos