Latest Contributions by CharlesMcNeel

I'm a little late to the discussion but wanted to get in here. WV numbers are this:     1 - Create Route 351 2 - Calibrate Route 2194 3 - Reverse Route 1 4 - Retire Route 15 5 - Extend Route 3 6 - Reassign Route 64 7 - Realign Route 10 12 - Cartographic Realignment 6379 TOTAL 9017 A note is needed.  WVDOT has two LRM's and these are numbers for NetworkID "1".  Further I'm not all that confident in those numbers since as I look at the NetworkID compared to the RouteID I see that they don't always match.  In other words, we use a different format for the RouteID between our LRM's so we can tell at a glance which network it is.  Problem is that doesn't always match the recorded attribute for NetworkID.  Makes me wonder how much we can glean from this table. ... View more

Meggie, They are two different workflows so clone is out. I could put the information in an extended table, we just had not used that functionality so far.  I would then, of course, need to add that to the workflow.  So far the description has been enough and has served us well.  I have already set up a test workflow that uses the Create job advanced step and saw that extended properties could be copied but first thought I would pose the question to avoid the addition of the table and setup of extended properties.  I will explore this more and may use the extended properties and take that opportunity to add other properties as well. Thanks for your help. Charles ... View more

Thanks Meggie for the reply. I will check that out to see if that will work.   To elaborate on my process.  I am trying to set up a workflow that will handle the addition of new roads into our system and other similar tasks.  So the process I envision is to create an LRS job to add the route into the network using versioning.  Then before that version is posted an event editor will add the events to the route.  But I want to keep the events in a version off of the LRS edit version in case something goes wrong and the event version needs recreated.  Once everything is QC'ed then it all can be posted to the default and all required data will show up in default at the same time.  We already have a workflow to accommodate event edits and I was trying to nest it within the other one to accomplish this but I wanted to pass a description from the LRS job to the event job. For instance, we may have received paperwork to add route 1 so a new job is created.  An LRS editor will add route 1 in a new version.  Once that is done I want to create the event edit job next that will describe what route events apply in a child version off the LRS version.  Currently we describe a job using the description field only and use the name just to show if a job is an LRS edit or an Event edit.  I want to try to show what is going on and where in the job list which can be confusing. I hope this makes sense. Thanks again, Charles ... View more

Thanks Clive! I looked at that page but noticed that the 10.5 and 10.6 pages were grayed out so I didn't think to try it.   Charles ... View more

Great! The patch fixed my issue.  Well at least the one I had with WFM Thank you very much Steven. Charles ... View more

Yes, it's #NIM099220. Thanks ... View more

Turns out this is a bug that ESRI knows about.  Hopefully they will get it fixed soon. In the meantime, the work-around is to add the input database each time you run the tool from WFM. ... View more