Replacing identical parts with iLogic configured parts... will it break existing assemblies?

[inund8]

My company has many parts where only 1 dimension changes, and currently these are all separate unlinked ipt's/idw's. I want to float the idea of converting these to use iLogic configured parts, so that the we can have one IDW with a table referencing the one unique dimension for each part number, so that all variations can be on one drawing.

What are the reasons we should NOT do this? My biggest concern is that it could break assemblies? If the ipt's are put back in the same folder after the iLogic creates the configured ipt's, will that still break things, assuming I only change the dimension? (i.e. not the geometry)

[dalton98]

Are you talking about Model States or iParts/iAssemblies? I can speak for model states... it didn't break assemblies, but there were odd things that happened with them that's hard to explain. We ended up creating all new parts/assemblies, but it was very easy with the built in 'Edit via Spreadsheet'. The only real problem we had was making sure to name the model state files differently from the original files in the project folder.