Sparx Systems Forum

Enterprise Architect => Suggestions and Requests => Topic started by: «Midnight» on April 23, 2007, 02:12:59 am

Title: API support for Export/Import Reference Data
Post by: «Midnight» on April 23, 2007, 02:12:59 am
There are methods for exporting and importing package XMI, as well as transformations and imports (forward and reverse engineering), but reference data seems to be unsupported.

Methods for doing this - probably via the Repository object - would be welcome.

David
Title: Re: API support for Export/Import Reference Data
Post by: Paolo F Cantoni on April 23, 2007, 02:23:20 am
Seconded (and Thirded)
(vote early and often!  ;D)

Paolo
Title: Re: API support for Export/Import Reference Data
Post by: fr3sh on April 23, 2007, 02:41:50 am
vote... i need it  :(
Title: Re: API support for Export/Import Reference Data
Post by: salayande on April 24, 2007, 10:40:46 am
API support for reference data is valuable. I support this.
Title: Re: API support for Export/Import Reference Data
Post by: pmullin on November 21, 2007, 08:01:14 am
I vote for this one too.  

Disseminating updated reference data to multiple users is a real pain.  There does not appear to be any sensible way to do this when using private EAP files that are synced via version control.   Ideally, this data should be part of the root package, so that it can be included in VC updates.   Short of this, writing an add-in to do the import would be reasonable, if the APIs were available.
Title: Re: API support for Export/Import Reference Data
Post by: thomaskilian on November 21, 2007, 08:10:36 am
Me too!
Title: Re: API support for Export/Import Reference Data
Post by: KP on November 21, 2007, 01:46:24 pm
Unsupported, undocumented, 7.0.818 and later:

Repository.CustomCommand("Repository", "ImportRefData", sXML)

or

Repository.CustomCommand("Repository", "ImportRefData", sFilename)

:-X
Title: Re: API support for Export/Import Reference Data
Post by: «Midnight» on November 21, 2007, 04:04:38 pm
Quote
Unsupported, undocumented, 7.0.818 and later:

Repository.CustomCommand("Repository", "ImportRefData", sXML)

or

Repository.CustomCommand("Repository", "ImportRefData", sFilename)

 :-X

But it is a beginning Neil.

Any way to filter what you export and import? Or do we just end up dumping everything, and replacing everything on the other side?

David
Title: Re: API support for Export/Import Reference Data
Post by: Paolo F Cantoni on November 21, 2007, 08:53:39 pm
Quote
But it is a beginning Neil.

Any way to filter what you export and import? Or do we just end up dumping everything, and replacing everything on the other side?

David
Just to be clear, import is additive.  If the item already exists, then it's updated.  If its new, it's added.  If it was deleted - too bad...  It's still in the target.

There is no "true" replace this set with that set - as with package import...

Paolo
Title: Re: API support for Export/Import Reference Data
Post by: peter.zrnko on November 22, 2007, 12:00:45 am
And it will be very nice to Version control Reference data from EA.

It has a
 big   + nice control in the same way as packages
 small - necessity to check out Reference data before modifying them.
Title: Re: API support for Export/Import Reference Data
Post by: «Midnight» on November 22, 2007, 04:41:20 am
So, a desirable option would be to replace or refresh the settings. Of course this should be a parameter in the API call as well.

David