In trying to create a datum curve through a points table with 88 points, it fails if I select the points group from the browser. However, if I select each point in order individually, it works. Any Thoughts?
Copy of the file is included
Solved! Go to Solution.
That was it. But now a follow-up question. I will have a model with a number of these point tables and curves. There will be situations where i need to use a new point table which is very similar, but one that does have slightly different point locations. Is there a way to replace the points in the table without a lot of button pushing? I will have a number of them, and it takes a while. And I will be doing work that references the table and curve so I would rather have the points table update, rather than creating a new table. Is this something that can be scripted (not necessarily a map key)?
It's really easy to delete the existing points while you're editing the point feature. Simply select the first item in the list, hold down SHIFT, select the last item in the list, right click, and select 'Delete'. At this point (no pun intended) you can simply re-import your updated points lists (just like you one your provided to this thread.) You may find it easier to rename it *.pts. Also adding or removing points from the point feature should not cause the subsequent curve from points feature to fail as long as it can form a continuous connection (with no duplicates in the middle.)
As far as automation, I use SmartAssembly here to do something similar. In my case I'm reading in 14,400 point coordinates from an Excel file, adding these to points arrays, and then updating the points features in the Creo models with the new data. Very simply to do, but requires owning this software. If I didn't have that available I'd probably try making a mapkey that would delete all the points in a feature and then prompt me to select the new points file for importing.
Doing the mapkey to delete the points in the open table, and then prompt for the new table works, but it's hundreds of tables. With your knowledge of smartassembly, is programming something like that complex if one had smartassembly? It's really the couple of steps that you mentioned, set within a loop, where the names of the tables increment through a preset sequence (TURN01_V1, TURN01_V2, TURN02_V1, etc).