- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
About the error...did you change that full file name being specified in the code to the downloaded part document's new path and name? If not, you will need to do that before it will work.
When editing an iLogic Form, and you have the main, top line item (for the overall form, not something within the form) selected, you will see a property called "Show on Place Component", with a Boolean type value available at the very bottom of the form's properties, under the Behavior sub group. If you turn that on, that will cause this form to show when inserting this document into an assembly as a component. However, iLogic Forms to not generally mix well with trying to control multiple ModelStates. Each ModelState represents a different Document within the one file on disk, and when you launch a global iLogic Form, it will generally remain focused on the document that was active on your screen when the form was first opened, and will not switch its focus to another document while it remains open. When it is an internal form, its focus will remain on the document that it is saved within. However, I am not sure how it would be able to change what ModelState the component should represent, because it will already be focused on whatever ModelState that was currently active in that model. Folks have been trying to change ModelStates using a Multi-Value text type UserParameter to populate a drop-down list in their iLogic forms without much success, because you are only changing the value of that parameter within the currently active ModelState, not the other ModelStates. It may be possible through the use of additional iLogic rules that are reacting to the value changes in the form though.
Wesley Crihfield
(Not an Autodesk Employee)