PDA

View Full Version : How to find the next unused Type Mark or Mark?



Duncan Lithgow
2012-07-31, 01:24 PM
I'm doing some cleaning up in some models and want to get rid of warnings about duplicate Type Mark and Mark values. Other than trial and error does anyone know of a way to just find the next unused number?

Dimitri Harvalias
2012-07-31, 01:45 PM
Quick schedule sorted by type mark/mark, highest to lowest?

Duncan Lithgow
2012-07-31, 01:53 PM
Yup, a Multi Category schedule - you got there just before me I think.

- Parameters: Type Mark and Type
- Filter by "Type Mark is greater than than 0"
- Sort by "Type Mark"
- Don't itemize every instance

Now all the places where the same Type Mark is used on more than one type the Type column is blank. I just delete the Type Mark and I'm done - and the ones I've already deleted are not on the list because of the filter. Same idea could work for duplicate Mark values - don't know if they're allowed to be blank though...

Nice.

Duncan Lithgow
2012-07-31, 01:58 PM
Grrr doesn't quite work. Why am I not getting types from all categories? Every type has a Type and a Type Mark doesn't it?

And I thought that deleting the Type Mark value stop it being a duplicate, there simply is no value. I've misunderstood something.

Dimitri Harvalias
2012-07-31, 04:02 PM
Why are you filtering? I thought you just wanted to know what the next value was so when you found a duplicate you could assign the next number in line. Am I missing something?

Duncan Lithgow
2012-07-31, 08:18 PM
Why are you filtering? I thought you just wanted to know what the next value was so when you found a duplicate you could assign the next number in line. Am I missing something?

Sorry about that. My actual aim is just to get rid of the warnings - once I discovered that deleting the Type Mark avoided the warning I switched tactic. So now I'm just looking for fast ways to sort schedules so I can find the Type Marks which are duplicates and delete them. What is annoying me is that I can't make a schedule which catches objects from all categories, really a pain when trying to fix this type of problem.