Wading my way through OBD changes.
I have set:
TFDIR_PART = $(TFDIR)Part/
and have files in this location, but the families and parts don't appear when I start OBD.
Any reason why this would happen?
Hello Bear,
Just tested it, I could see parts and families in Part & Family Editor.
Is there any error message that you are getting?
Regards,Aniruddh
No, just empty editor, but the path is showing. Weird.
Bear,
If the path is showing correctly, are you able to add a new xml file directly from the Family / Part Editor?
Just to re-confirm, are the files having the xml extensions?
Best Regards,
RJ.
Part of my job today RJ. I'll report back.
FWIW, the delivered values for TFDIR_PART are:
$(_USTN_WORKSETSTANDARDS)Part\;$(_USTN_WORKSPACESTANDARDS)Part\;$(TFDIR)Part\
That covers the workset, standards and dataset paths. Using only $(TFDIR)Part\ would exclude the workset and standards.
That's what I want Steve, not interested in 3 locations for my build when I only need 1. Is that an issue?
As long as all of the parts are available as required - some components do have Family:Part defined at the DG catalog level - no, I don't think it should matter. FWIW, our delivered \worksets\Workset_Name\Standards\Part and \WorkSpaces\Building_Examples\Standards\Part folders are usually empty anyway, leaving everything at the dataset level.
Since TFDIR_PART is simply = $(TFDIR)Part, how is TFDIR itself defined?
That was my take as well Steve. When we build a dataset from scratch we usually take a copy of the AU dataset and change it to suit. I'm going through that now, but finding lots of speed bumps. I'll play a bit more and see why these aren't appearing in the editor and report back.
Thanks,
Sounds like a plan. One other thing though - can you check whether TFDIR_PART is being defined more than once to the same location, and if so, whether the operator is the same in both instances?
Will do.