I am trying to configure managed attributes in Team Server, but the attachments I have added to enterprise data dictionary do not show up on the Admin -> Manage Attachment Attributes page. I have included a screen shot of the EDD, so you can see that the attachments are present and a screenshot of the Manage Attachment Attributes page to show that they do no show up as available.
I'm looking at this and the other post you had and it seems like in Data Architect you have this:
What you have Attachments, and under there you have two folders, Column Mapping and User Interface Location. These are just folders which do not contain any attachments. What you need to do is right click on "Column Mapping" or "User Interface Location" and then choose New Attachment. So you'll end up creating something like this:
Once you've done this and the model has synched, then you will see "Column Mapping 1", "Column Mapping 2", "UI 1", and "UI 2" there under managed attributes in Team Server.
I did figure that part out, but it is still not working. I renamed my two Attachment Types to Attribute Property and Entity Property and add a User Interface Location Attachment to the Attribute Property Attachment Type. In addition, I added a Term Property Attachment and also added a User Interface Location Attachment to it as shown below:
When synching with Team Server, the only thing that happened is that the rename of the original Attachment Types is reflected, but the addition of the attachment and the addition of the Term Property attachment type do not show up.
I find it hard to believe that it is this difficult to get all of this synched up. And, yes, I have updated the solution repository and updated the search index.
Hi Stan, I am also facing this similar scenario. I can see the attachment bound to the entity i have bound it to in Team Server ( to the point of the Reporting repository: Team Server being in sync with the DA repository). But on the Managed attributes section, i don't see the attachments to effectively bind with glossary terms etc.
below shows blank under Managed Attributes
I did get a "resolution" on this. I was creating the attachments in my enterprise data dictionary (EDD). If I bound that attachment to an item (e.g. attribute, entity, etc.) in a data model to which my EDD was bound and then checked in my model, the attachments would show up in Team Server. The problem, however, is that the particular attachments I was creating were not intended to be bound with an entity or attribute. Rather, they were being created to bind them with a term in Team Server.
After working with Idera support for a while, a workaround was devised. We discovered that I didn't need to associate the attachment with an object in my data model. All I needed to do, in addition to creating the attachment and checking in the EDD, was to make a change to the model file in which my EDD was created. Once I did that, the attachment showed up in Team Server. However, it was determined that just checking in the EDD should have sufficed to sync with Team Server. I shouldn't have had to make any other changes to the model file. I also discussed this with Ron Huizenga (the ER/Studio product manager). He agreed with that assessment and was going to raise an issue to get it fixed in a future release.
The bottom line is that you should be able to get the attachments to show up in Team Server if you modify the model file and save it. Technically speaking, I checked out the diagram, modified diagram properties from the file menu and checked the diagram back in. Once I checked it back in, it sync'ed with Team Server.
Thanks for taking the time to explain the resolution you found. I'd like to make sure i state where i stand so we have a common understanding. In my case, i notice the ER DA data dictionary attachments (defaults, domains, attachments etc) are in sync with the Team server for the given project. I can see the attachments in the Team Server, ER Objects. However, under Admin->Managed Attributes, i don't see the data dictionary attachments. This is my problem statement.
Is your resolution around the above problem statement? Just wanted to make sure we're baselining off the same issue.