APPLICATION - PRODUCT ENGINEERING - Classification specific properties question/problem

ascallonisi - Thursday, July 23, 2009 9:34 AM:

Hi, I am an Aras newbie and I am having a problem in following an example from the "Print of Online Help - Aras Product Engineering.pdf" manual p.18  on Innovator 9.1.0:

"To add a class specific property:

1. From TOC, Administration folder, select ItemTypes, search for Part, and open Part for edit.
2. Add a new property, name it Build Number.
3. Click on the Class Path cell of the new property to open the class path form. Select Software, and exit.
4. Save Part.
5. From TOC, Administration folder, select Forms, search for Part, and open the Part form for edit.
6. Click on the properties icon . Select Software's Properties, build_number.
7. Place the new field on the form.
8. Select the Field Physical tab. Uncheck the Visible check box. This property will automatically become visible when a Part classified as Software is created, but will remain invisible for all others.
9. Save, Unlock and Exit from the Part form."

All first 5 steps completed succesfully, but I can't manage to find the "properties" Icon and select the "Software" specific "Build Number" property (step 6 in bold).

I somehow managed to insert "Build Number" as a field, but when I open the form for creation of a new part, it's present even though it's "Software" specifc...

Is there a way to prevent it to appear in the "New Part" form unless I change its type to "software"?

Thank you.

BR,

Alessandro

Brian - Monday, July 27, 2009 7:50 PM:

Hi Alessandro,

Not sure if this has changed since 9.02 in which it works.

Provided your step 3 is completed correctly. Open the form for edit. Place a text field on the form. Go to Field Type and select the Build Number as the data source for the field. Do not uncheck the "Visible" option in Field Physical and save the form.

This worked for me.

We haven't downloaded 9.1 yet so I can't help if this doesn't work.

Cheers,

Brian.

ascallonisi - Tuesday, July 28, 2009 11:46 AM:

Hi Brian,

thanks for helping out, actually it looks like  the problem is a little trickier...

First, there is a legacy bug on 9.1 (011982), as described in the following posts:

http://www.aras.comhttp://www.aras.com/Community/forums/p/511/1462.aspx#1462

http://www.aras.comhttp://www.aras.com/Community/forums/p/372/1042.aspx#1042

which prevented the correct operation of Forms builder.

Furthermore, the complete  procedure for setting up a form for a "child " of Part is better described in:

http://www.aras.comhttp://www.aras.com/Community/forums/p/404/1158.aspx#1158

and is a little bit more "elaborated" than what described in the manual (although much more powerful IMHO)

Ciao,

Alessandro

dlhayes - Tuesday, August 25, 2009 1:21 AM:

Hi Alessandro,

I put ARAS away, as this issue defeated my attempts to beat it.. the funny thing is, I have come back to re-evaluate it, searched the forums for this problem and found you.  Thinking this issue was resolved, I followed it through to find my original posts! dang.

If you have any luck with it, let me know.  I am still in deep and I have returned to the problem, although with no solutions at this point.  I have not tried, but I am close to ignoring the cool inheritance feature of the form (and the designed intent) and generating unique forms for each "child".. It certainly shakes the confidence in the system, but others don't seem to have this problem,  I do not know why either. 

Make sure you do the fix from your previous links, or your experience will be unpleasant for sure.

Regards

Darren

Manu31 - Wednesday, April 2, 2014 8:14 AM:

Hi Alessandro,

My current issue is near like your.

I would be very interesting by the procedure described in the link you copied in your post, but today the link is not available.

http://www.aras.comhttp://www.aras.com/Community/forums/p/404/1158.aspx#1158

Please, have you got a copy of this procedure ?

Today, I can add and display customized field on all the Part sub classification Component, Software, Material... but even I used the Class Path attribute as described in the doc, I fail to only used this new attribute in only one sub classification

Thank's in advance for your help

Best regards

Manuel