Text parameter in Content Center table

[andrewiv]

I'm trying to make a column on a custom content center part drive a text parameter in the created part, but it is not working.  I have the text parameter in the part and publish it to the content center, then create a column in my family table and set the data type to string, then in my family properties I map that column to the user text parameter.

It give me the error that the column type does not match the parameter type.  

When I generate a part from this family the values are not pushed to the parameter.

Is there something I'm missing here, or is this not possible?

[AndrewHumiston]

Good morning Andrew.

Would you attach the file you are creating the content center part from? this will allow me to recreate it quickly and see what you see.

look forward to helping you solve this.

[andrewiv]

I think the issue is with any part that you are trying to push a text parameter to, but here is a test file that I'm having the issue with.  I took this file and published it and added one column and then mapped it to the test parameter.  The parameter doesn't update on standard or custom parts.

[AndrewHumiston]

thank you, i'll test this and get back to you with what i found

[AndrewHumiston]

Andrew,

I did some testing, and you cannot drive a text parameter from an iProperty. such as you are exporting the value from your parameter list into an iproperty, this doesn't allow for you to change the iproperty and update the parameter.

Is there a reason you need the text as a parameter? We could map and set up a custom iproerty that would do the same thing.

please let me know your thoughts.

[andrewiv]

I'm not trying to drive the parameter from the iProperty, it's the other way around.  I'm trying to drive the parameter from CC and then have it drive the iProperty.

[AndrewHumiston]

I understand. that parameter is not changeable inside a CC part. Numeric parameters are changeable. that's why I was asking if you could skip the parameter part of this and just use a custom iproperty. that can house the data. why do you need a text based parameter?

[andrewiv]

The issue comes from something that was set up in our templates and using parameters exported to iProperties.  After my original post, I did figure out that it works fine if I just drive the iProperty and delete or uncheck export on the parameter.  But I still think it is odd that we cannot drive a text parameter with the CC table.  I am able to get around it but there might be a legitimate reason why we would need the ability to modify a text parameter later.  If they cannot be driven by the table then that should be stated somewhere and it should not allow you to map a column to a text parameter.

[AndrewHumiston]

i agree that is odd. i will send this up to Autodesk, and bring it to the attention of the neccarry people. do you want me to tag you in on the ticket?

[andrewiv]

Sure, you can tag me in the ticket.

[andrewiv]

@johnsonshiue were you aware of this limitation?  Is this an oversight, bug, as intended, or something else?

[johnsonshiue]

Hi Andrew,

Indeed, it is not a supported workflow. It was partially due to iPart not supporting text parameter either.

Many thanks!

[andrewiv]

Thanks for confirming that.  I have added this to the idea station - https://forums.autodesk.com/t5/inventor-ideas/text-parameters-in-content-center/idi-p/12888854

[clutsa]

I'm running into the same issue. We have a part that looks like a ladder. There are four options on the shape of the "rungs" I can drive everything by setting a unitless parameter and set the features to suppress if that field does not equal it's assigned value. The problem is how does someone adding to the table know what option 3 is? So a made a text property and iLogic that checks the text and sets the unitless value as needed. However now when I publish to content center the text fields turn to to "real" data type and won't accept text.