relationship cardinality details not found in .twb xml in tableau - tableau-api

I am trying to find the relationship cardinality details from the .twb file but not able to find it.
From the .twbx tableau application On unzipping it a .twb file is generated which contains the metadata about the application in xml format even though it has a relationships tag but no cardinality information is obtained in that.Where can I find them in the xml structure

Related

Importing multiple correlated XSD on LiquidXML

I have multiple correlated XSDs that needs to be uploaded in order to create a large library, but I haven't had any option to do so on the interface. The option to select XSD is only limited to one file.
Is there a way to go around this issue?
You need to create a 'Super Schema' which will include or import all of your top level schema.
Please see the knowledge base article:
Liquid XML Data Binder - Super Schema

Oracle Data Modeler generated column name from datamodel too long

I'm trying to create a datamodel in the Oracle Data Modeler module that is available in Oracle SQL Developer. I would like to maintain my data dictionary from this model. To do this (I think) I need a generated DDL file for which the attributes are not longer than 30 characters.
I have just discovered Oracle SQL Developer and am completely new to creating these kind of models. What I have done so far. I have created a logical model and have engineered it to a relational model. From the relational model I can then generate DDL scripts that I can run on the database to make the changes I want.
When doing this I run into a problem. When engineering the logical model to a relational model I can see that the foreign keys I have made become more than 30 characters. This is because it seems to generate the name as (see picture)
From searching it seems you should be able to fix this with naming standard templates. I have looked for this menu option but can't find it. I have found the name abbreviations functionality for which you can upload .csv files but I think this is for something different.
Rightclicking on the logical model in the datamodeler browser view gives me the opportunity to Apply naming standards, but this gives me a message that I should turn off the keep as the name of the originating attribute option (see picture). I have looked for this but can't find this option.
My version of Oracle SQL Developer is 4.1.3.20, Build MAIN-20.78.
Please let me know if my story is not clear. Thanks.
Generated column name
Applying name standards message
You will find the option under Tools/Preferences/Data Modeler/Model/Logical

Can I automatically associate an XSD schema with an XML document

I'm editing a lot of XML files using Liquid XML, I can associate a schema with the document by adding a schemaLocation attribute, but this is not practical as I have lots of files and I can't leave the attribute in as the upstream processor doesn't like it!
Is their a way I can associate a schema with a group of files?
There are a few ways to associate XSD schemas with an XML document.
Schema Location Attributes
If the XML Document contains a schema location attributes (xsi:noNamespaceSchemaLocation or xsi:schemaLocation attributes), then the schemas pointed to are loaded and used for validation and intellisense.
Namespace
The namespaces declared in the XML file are used to lookup schemas from the Schema Library. If a namespace in your XML file matches an entry in the schema library then all the schemas for that entry are loaded. You can also add your own entries to the Schema Library (more about this below).
Manually associating schemas
You can manually associate schemas with your XML File. Use the "Xml Document to Schema Mappings" form to select existing entires in the Schema Library, or "Add Schema file" to select a single XSD file to associate with the XML document. These settings are then remembered then next time the XML file is opened. This is particularly useful if your XML file does not contain a target namespace, as automatic matching is therefore not possible.
Manually associating a schema with an XML File
You can control the schemas that are associated with your XML File using the "Xml Document to Schema Mappings" form.
The form show all the schemas that have been added to the Schema Library. At the top of the list are the schemas that have been found in your XML document (ie via xsi:noNamespaceSchemaLocation or xsi:schemaLocation attributes).
Checked - Explicitly included schema. The schema is used regardless of whether the namespaces appear in the XML document. This can be useful when associating schemas with XML documents that do not contain any namespace information.
Unchecked - Explicitly exclude schema. The schema will not be used regardless of whether its namespaces match the XML Document. This is useful when you have several versions of the same schema, and they all have the same namespace, or where the schema is so large intellisense slows down the XML Editor to an unacceptable degree.
Indeterminate - Automatic schema selection. If the namespace in the schema entry match the ones in your XML file then this entry will be used.
This is the default state for all entries.
Adding your own Schema Library Entry
If you have a set of schemas that are not in the standards library you can add your own entry.
Note you can add several schema files that may not necessarily be associated with each other, say for example FIXML contains annotations that in your documents contain XHTML, you could also add the XHTML schema. If you did this it would be a good idea to de-select the XHTML namespaces from the trigger namespaces listed (so this standard is not used when an XHTML document is opened, only when a FIXML document is opened).
And Finally the Answer
If your XML documents are all in a given namespace your best bet is to create a Schema Library Entry. This will be automatically associated with any XML documents that contain that namespace, so you will get validation and intellisense automatically.

How to define requirement describing csv file structure in Enterprise Architect

I am learning to use Sparx Enterprise Architect for requirements management. I am wondering, what is the best practice, or any practice to describe CSV file structure (i.e. header names and their types) that will be imported by designed system?
Do you use taggeed values, or simply just "Notes" area? Or maybe just link sample csv file, but then, how to include it in printed documentation?
Thank you for advice!
UML is, of course, not good at describing structures such as CSV formats. You can create classes with attributes "col_1", "col_2", etc, but the simplest way is probably to add a linked document to the requirement (right-click and select Create Linked Document).
The linked document can be included in a generated document quite easily. In the template editor, simply select the Linked Document node under the Element node.
These linked documents are stored inside the EA project. They are RTF, so they are very limited compared to other formats, but they support tables and other basic formatting, which is usually enough for requirement details.

Can the ///summary be auto filled by SQL Server descriptions in EF4 Entities?

Our company is in the middle of evaluating a couple of different ORMs and we are currently looking at the EF4 side of things.
I have a small question that I hope someone here can answer...
In our generated EntityDataModel.Designer.cs file all our Entity classes (and the properties within them) have a ///summary with the sentence "No Metadata Documentation available".
Is there any way to have these picked up from the Description Property on the columns from SQL Server?
I can see there is a documentation property within the edmx file but they are all blank.
Obviously its not a deal breaker in our decision - but it would be nice.
Thanks for any advice
Aaron.
Yes, documentation properties are blank in EDMX because you must fill them yourselves. EF doesn't load columns descriptions defined in SQL Server.
These columns descriptions are stored in sys.extended_properties and have MS_Description as a name. Theoretically you can modify T4 template (EFv4) to load descriptions for columns and create comments but it would be a lot of work to do. You will have to:
for each scalar property you will have to search metadata to get column and table name and query DB to get a description
That is a lot of work and having T4 template opening connection to database is very uncommon.