cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

ability to link all parameter types

ability to link all parameter types

Boolean (true/false) and string (text) parameters can be quite handy. What I think would be a real improvement is being able to link them like numerical parameters.

 

At the moment doing this right for a boolean parameter requires the following steps:

  1. make boolean parameter has_feature_x in source file
  2. check key behind parameter
  3. add parameter to form
  4. make numerical counterpart has_feature_x_num
  5. convert boolean to numerical:
    If has_feature_x Then
        has_feature_x_num = 1
    Else
        has_feature_x_num = 0
    End If
  6. check export behind numerical parameter
  7. link source parameter in destination file
  8. make boolean parameter has_feature_x in destination file
  9. convert back to boolean in destination file:
    If has_feature_x_num = 1 Then
        has_feature_x = True
    Else
        has_feature_x = False
    End If
  10. write iLogic rule in destination file for feature manipulation:
    If has_feature_x Then
       Feature.IsActive("feature_x") = True
    Else
       Feature.IsActive("feature_x") = False
    End If

 

This has a lot of steps that do not add anything directly, and leave room for error.

 

With the ability to link these parameters, it could work with these steps:

 

  1. make boolean parameter has_feature_x in source file
  2. check key and export behind parameter
  3. add parameter to form
  4. link source parameter in destination file
  5. write iLogic rule in destination file for feature manipulation:
If has_feature_x Then
   Feature.IsActive("feature_x") = True
Else
   Feature.IsActive("feature_x") = False
End If

 

This would:

  • Reduce the required amount of iLogic code by 50-67%
  • Guarantee a true/false value to work with
  • Make the iLogic code less prone to mistakes

This in turn would make it easier for technical drawers that are a little less tech-savvy to automate different configurations. Since most of our products just have a different configurations this this would improve the speed with which we improve our drawing speed.

3 Comments
CamperUnhappy
Advocate

You've got my vote.....

 

I just thought I had figured out a crafty way to get around an issue I'm having with parts lists and BOMs with linking a Boolean parameter only to find out that I can't export a Boolean parameter....why?  This seems like a seriously simple piece of functionality that could be implemented but it's not available.  It's crazy.  Now I have to write logic to tie a custom property to a parameter and hope that the link stays reliable.  I spend so much time trying to find ways to get around SIMPLE little issues like this it actually makes me sad to think about how much time I spend on this kind of stuff instead of actually doing my job.

Anonymous
Not applicable

This would very helpful when setting up parameter templates from excel. 

 

I usually have up to 400 parameters in an Inventor file.  Entering them one at time in Inventor is very clunky and not user friendly. It is hard to reorder them in Inventor, if not impossible.  So that ability to utilize Excel for the prep work would be helpful.   

 

I can set them up in Excel then order by Alpha/Numerical so things are easy to locate in Inventor.  Them embed them in the document as I don't want the spreadsheet to be outside the  Inventor model.

gcoombridge
Advisor

This would definitely help! I use Ilogic to send parameters back from assemblies but I would like the ability to include text and boolean parameters in derive operations - i.e sending out components from a multi-solid master file to individual parts. 

 

Additionally, because the interface for adding user parameters is clunky I like to rapidly import them from excel - but boolean and text parameters don't come from there either... Please upgrade this Autodesk!

 

Cheers,

 

 

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea