Adrian Support

[Adrian Support]

Thought that may be the case – a few others have asked and we have considered including but our delay in doing has been the decision on UI.

Would you be be happy with something like a menu option on the context menu so that when a package is selected the extensions menu would provide “eaDocX | Open in Excel | Class properties (there may be a better name)” it would output class (table) properities.

This output columns could be:

ElementType (Attribute or Method) | Class Name (as a mandatory column to ensure that you know the parent) | Name | plus any other columns you select.

There would be one per row so would provide the ability to compare/import as any other element.

Does this cover your requirement?

Regards

eaDocX support

I’ll discuss

[Adrian Support]

Hi

I assume that this is only happening when you use for the first time (migrate), and that newly created documents work fine thereafter. That’s what I can see – let me know of otherwise.

I’ll look at the code that handles the conversion between versions and get back to you.

BR

eaDocX support

[Adrian Support]

Hi

eaDocX can output a summary of the attributes / methods for a class so for a data model which will provide the information of the properties for each element – see the attached screenshots.
To perform this:

1. create a new workbook
2. select the package containing the tables[/
3. In the columns tab – check “Display Compound Attributes” – it is near the bottom of the columns tab
4. Select desired columns for output include “Attribute summary” to output table properties
5. Select EA output button to initiate export

This output will just list the element properties. If you want to get more detail for each property then you can select a single table element and initiate the export of the attributes (properties) for the single table (see screenshot for menu selection).

This operation will output the properties, 1 per row, for the single table. This output will allow you to select more detail; with the advantage that you can edit the detail and update.

I hope that provides what you need.

BR

eaDocX support

[Adrian Support]

Hi,

In eaDocX you can save and load profiles from the File menu. This allows you to create a profile with the common elements. You cna use this as the base and then tailor versions for your different customers and save them with a descriptive name for use later. We don’t support the export of or import of single profile elements from or into a profile.

The details of what can be done within eaDocX in terms of using existing profile information is outlined in the section of user guide on “Sharing document profiles”.

The information is stored in a readable xml file – if you edit you do at your own risk 😉

I hope that helps.

Regards

eaDocX support

[Adrian Support]

Hi,

In terms of your new requirement I am sorry to say that, within the current export rules we have within eaDocX, we are not able to restrict the depth of children that we output.

One option would be to replace your Activity Partitions with Packages – see attached screenshots which illustrate the structure in the project browser, a diagram and the output that you would see if you output from the package “Component test”
In this way you will then be able to select not to include the children. Often a package is a better way to partition information.

Would this work within your model? or is there a specific reason for needed to enclosure the components within elements?

Regards

eaDocX support

[Adrian Support]

Hello Sudhakar,

Thanks for the screenshots which explain the situation.

To start with if you have a diagram selected and initiate the eaDocX/eaXL export then it will ALWAYS output all elements of the diagram. The export from a diagram is intended to allow users to group elements in a different way than their structure and output a consolidated set.

To output the elements you require – i.e. to output the “level1” components within the package you:
1. select the package
2. Then from either
– the main Extensions menu select “eaDocX | eaXL | Open package”
or
– using the right click context menu in the project browser “Extension | eaDocX | eaXL | Open in Excel”

This will produce a new Tab within EA and populate with the initial level of elements in the package i.e. the owner package and components 1,2,3,4 – not their children

Which is what I think you want.

If you did wish to then change what is included – for example:

– to remove package elements from output then uncheck “package” in the “Elements” Tab
– to modify required columns on the “Columns” tab
– to include children then check the “Output Child Elements” on the “Columns” tab.

I hope that helps and you are able to produce the information you require.

Any other questions do ask.

BR

eaDocX support

[Adrian Support]

Hello

Thanks for the additional information, however from your description I can read many different scenarios – it would probably help if you can email us an example as well as the report spreadsheets that you have produced, this will allow us to share some common ground, view what you are starting with and make it easier to make suggestions on how to achieve what you want (assuming we can do it :laugh: )

If you can email the snippet (xmi or eap) to support@eadocx.com that would be great.

Thanks

[Adrian Support]

Hi

Not entirely clear on your issue.

You can produce a list of elements (e.g. components) and not include the children by unchecking the “output child elements”
and all elements list will include all the detail for all columns.

However I suspect this is not your issue – are you saying that you want to output BOTH components and their children BUT exclude the attributes/columns for the children? BTW: Not a mechanism to do this at present.

If you can clarify then I can advise.

Regards

[Adrian Support]

Hello

Just built a fresh VM with EA 10, eaDocX and Office 2003 and as you say it is possible to save files with the wrong extension although my version of XL didn’t complain.

If you use the “file | save as” menu it will name the file with the extension .xlsx which is incorrect 2003, I checked and looks like the internal format of the created file is correct, so by renaming the file from say bookxxx.xlsx to bookxxx.xls it should work.

Alternatively, if you use close the tab and save the file from the presented dialog it will save with a .xls extension.

In all cases the content appeared valid – so it is an extension issue. Interestingly we didn’t get a warning but they may due to differing configurations. It would be useful to know that by renaming you can open the file OK.

Regards

[Adrian Support]

Hi

Both the items you identified were not included as requirements in our original Use Cases, however they are being added and should be included in the forthcoming release 3.3. Information about this release will be on our web site soon.

regards

eaDocX support team

[Adrian Support]

Hi

Sorry a bit of confusion between us on terminology and hence verifying your issue.

We have been able to reproduce your examples exporting from EA.

In fact the examples you presented were not included in our original Use Case for export of single elements.
The issue is easily rectified but need to check with the chief designer before inclusion in release.

Will advise in due course.

[Adrian Support]

Thanks for reporting these issues, which on a quick check look like they are related – we will look into and come back soon.

Regards

eaDocX support team

[Adrian Support]

Hi Werner,

Many thanks for checking and confirming that changing the regional settings ensures that eaDocX works fine. I hope you like what you see and that you see how useful eaDocX can be.

And you are correct that we can make calls to Excel and specifying regional settings to overcome this issue; I did some simple tests using these API’s. However we still need to review all Use Cases relating to our interactions with Excel as well as ensure that in other environments we don’t have a negative impact. So still some checking to do; it could be a bit dangerous to just apply a quick fix – and potentially upset others;-)

Don’t have a date yet but will be flagged when we do.

BR

Adrian

[Adrian Support]

Hi Werner,

Well I took the description directly from MS support so i do believe they were referring to an a version for Office.

However in having a quick look there are Multilingual User Interface Packs for Office 2003 but can’t find versions for 2007!

In fact looks like this was a common question – so probably need to explore further. Many of the comments I can see state that each version of Excel is single language – which creates an issues with a mixed language situation such as yours where you have an English version of Excel with non-English regional settings.

BR

Adrian

[Adrian Support]

Hi Werner,

I’ve spent some time looking at the problem you identified and been able to reproduce the Excel bug exactly.
And yes it is due to running an English version of Excel on a computer for which the regional settings for the computer are configured for a non-English language.

As in the link I sent previously (http://support.microsoft.com/default.aspx?scid=kb;en-us;320369) this is a Microsoft Bug and looking at the solutions it looks like the quickest, based on the Microsoft support answer, is for you to install the Multilingual User Interface Pack for your version of Office.

This is the first time we have seen the error – and will be looking at it further as we want to ensure it doesn’t impact users, however the other solutions require code changes and the extent of these is unknown until we have reviewed further, and of course we then need to make the changes and do regression testing, so not a quick solution.

You may also be able to change your locale temporarily and test in English(!) – I assume this should work.

I know this is not the response you want to hear (or we want to send), however I hope it provides you with a workaround to explore eaDocX further.

BR

Adrian

[Author]

Posts