Jump to content
  • 1

A more robust BATCH CONVERT


Jim Smith

Question

I think this request may have been mentioned in another post, so forgive me if this is redundant. 

I feel a more robust BATCH CONVERT protocol is necessary. It seems to me that we spend far too much time re-building or starting from scratch symbols and templates. For example, we started with an almost pristine new container on our 2017 Template but given the number of odd-ball things going on we'll have to start from scratch with the template & ditto for a who knows how many symbols. 

Templates and symbols should be a seamless transition. Could it be the importation of Workspaces? Shouldn't happen.

One substantial improvement that  should be considered is an alert that identifies suspect elements so one knows not to include these items in the Batch Convert. 

In the meantime, to whom may I send the bill for these lost hours?

>:(

 

Link to comment

0 answers to this question

Recommended Posts

There have been no answers to this question yet

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...