Guillaume Finance

[Guillaume Finance]

It seems that the purpose of this feature is to work on a list of elements which results from an EA search, based on the returned CLASSGUIDs.
Hence any other column is ignored. It makes sense to me now that the Import/Compare/Export will work on a list of elements GUID, as I cannot modify other information that I doesn’t understand.

It would be useful however to have an export only feature to retrieve in Excel results from an EA Search (limited to CSV). What do you think?

[Guillaume Finance]

Hi Brian,

You need to use a separate eaXL function to export operations/methods.
Instead of using Open in Excel, use Open ALL in Excel > ALL Operations.

Note that SysML Blocks without any operation won’t be exported.

Hope this helps.
Guillaume

[Guillaume Finance]

One of our customers is facing the same issue i.e. the server returns the base-64 string error making it impossible to use either floating license. 🙁

[Guillaume Finance]

Hi Michel,

I used to achieve this with the Excel module.
Once you have your enumeration classes created in EA (which you can alternatively import via eadocx), you need to add a temporary attribute to each enum class so it can be generated in Excel attributes template.
Right click on the package to export > eadocx > Open All in Excel > all attributes.

Having said that, I found out that the latest eadocx version makes a difference between Classes and Enumerations. Whilst enumerations export ok to Excel, the attributes export doesn’t work for enumerations (it works for a class that has at least a single attribute). Something that needs to be looked at by eaDocX Support.

Guillaume

[Guillaume Finance]

I second an enhancement in this area. One way to achieve this would be a feature to create additional profiles for the same element type e.g. UseCase, UseCase (b), UseCase (c), etc.
When creating sections in the doc, the first element profile would be picked up, and we would have the option to select another profile if available.
Then of course eaDocX doc generation would have the find and process the right profile.

[Guillaume Finance]

I downloaded and tried version 3.6.2.5.

It almost works:
– when I add a section from the model view, I’m getting the following exception message :

[code]************** Texte de l’exception **************
System.NullReferenceException: La référence d’objet n’est pas définie à une instance d’un objet.
à eaDocXAddIn.mvFavouritesNode..ctor(String aGUID, DGDocumentProfile p, eaDocXTreeNode parent, Int32 aHeadingLevel)
à eaDocXAddIn.sectionNode.addmodelFavouritesNode()
à eaDocXAddIn.sectionNode.addChildren()
à eaDocXAddIn.cntlPreview.fillDocTree()
à eaDocXAddIn.eaDocXMain.mnuMVItem_Click(Object sender, EventArgs e)
à System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
à System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
à System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
à System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
à System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
à System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
à System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
à System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
à System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
à System.Windows.Forms.Control.WndProc(Message& m)
à System.Windows.Forms.ScrollableControl.WndProc(Message& m)
à System.Windows.Forms.ToolStrip.WndProc(Message& m)
à System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
à System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
à System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)[/code]

– I then click on Continue -> my new section has been successfully created (e.g. Section 5) and I have an empty section as well named “Section1” (it appears in Orange).
– If I delete Section1, it generates ok.

[Guillaume Finance]

Hi,

Has this enhancement been dealt with in the current 3.6 version?

thanks

[Guillaume Finance]

It will be useful to import relationships.

Regarding the package structure, the easiest I think would be to replicate EA CSV export/import i.e. the use of CSV_KEY,CSV_PARENT_KEY columns.

See Using Preserve Hierarchy EA Help

• This reply was modified 9 years, 9 months ago by Guillaume Finance.

[Guillaume Finance]

Hi,

I second the need for post-processing scripts in eaXL. I’ve defined several Package Browser VBScripts to overcome some limitations of eaXL, and it would be very useful to execute them automatically after an import from Excel to EA.
Even pre-processing could be useful (e.g. I have a “create dummy attributes” script that populates empty classes so that I can run an export all attributes to Excel).
Having the option to associate each script either with the Excel to EA or EA to Excel + define a pre or post would be really good.

Best regards,
Guillaume

[Guillaume Finance]

Hi Adrian,

Having the option to define the parent package of a package to be import into EA with its elements (classes, requirements…) would be useful.
I can see a workaround but it’s best for the users to have such feature native in the tool (eaXL).

Thanks,
Guillaume

[Guillaume Finance]

Great news, I’m looking forward to it.
When do you think 3.6 will be released this year?

[Guillaume Finance]

Could eaXL attribute import/export include “Pos” column (t_attribute) in the selection of columns?
This seems an easy way so that users could easily apply the right value on the Position column and preserve the sorting order from Excel when importing into EA.

thanks

[Guillaume Finance]

I’d like to use the Enumeration type with eaXL, however this type is not supported nor listed in the Elements tab.
Enumeration exists in the t_objectypes table, and used in the t_object.Object_Type column (if you create an Enumeration element from the UML Class toolbox).

Based on your explanation I would expect Enumeration to be listed, which is not. Could this be a quick fix in eaXL?

Thanks

[Guillaume Finance]

Hi Adrian,

It worked 🙂

thanks
Guillaume

[Guillaume Finance]

Hi Adrian,

I managed in the meantime to identify additional steps to generate “dummy attributes” via a script so I can export all classes and add new attributes in the Excel spreadsheet.
Maybe you could generate such attributes on the fly (and delete them after the export) ?

A few suggestions when you consider this enhancement :
– could you add support of the attributes Tagged Values for the export to Excel (import by manually adding TV columns work) ?
– could you format with a different colour columns that are solely for export purposes? e.g. I don’t think columns like Path, Name + Description are used when importing into EA, hence it would be useful to see those that don’t need to be populated.

thanks
Guillaume

[Author]

Posts