Hi CMDBuild team,
Currently i have succesfully imported 3 external database tables (supportcalls, emails, userinformation) using the connector wizard in version 2.2.2 (upgraded today, yay). However i cannot seem to create a domain relation between the classes. How do i accomplish this? The manual is somewhat vague on this topic.
On another note, in the near future i also will have a usecase for 2 database tables from 2 different databases, but need to be related to each other. I have keys in both tables that be used for linking those tables. Can i use an (a)Synchronous task for this? I fail to find examples for this type of functionality, any hints would be appreciated.
Previously Tecnoteca wrote:
The connector wizard at this time can not import relation tables.
However, if one of the loaded attributes is a reference attribute then the relation is automatically created.
CMDBuild Team
Could you elaborate on
this?
For example, how should i create the MySQL view? And how should i create the attributes in CMDBuild in both master and slave class?
Previously Tecnoteca wrote:
The connector wizard at this time can not import relation tables.
However, if one of the loaded attributes is a reference attribute then the relation is automatically created.
CMDBuild Team
Let me clarify my previous question and lets take a more known example: OCS inventory
2 tables, hardware and softwares. The softwares table has a hardware_id column as a foreign key to the hardware table.
So the steps are:
- create a view for the hardware
- create a view for the software
- create a hardware class
- create a software class
- create hardware_software domain 1:n
For me it's unclear how to proceed and create the task. Which columns do i need and which attributes need to be defined?
Your example can not be implemented with the wizard connector.
In the current version the connector wizard is a fast solution for simple needs.
If you need to syncronize CMDBuild from OCS Inventory I suggest you take a look at the basic connector and at the advanced connector in the CMDBuild Connectors Manual.
Or you can write a small custom application and update CMDBuild through its SOAP webservice (in January will also release a REST webservice).
CMDBuild Team
Previously Tecnoteca wrote:
Your example can not be implemented with the wizard connector.
In the current version the connector wizard is a fast solution for simple needs.
If you need to syncronize CMDBuild from OCS Inventory I suggest you take a look at the basic connector and at the advanced connector in the CMDBuild Connectors Manual.
Or you can write a small custom application and update CMDBuild through its SOAP webservice (in January will also release a REST webservice).
CMDBuild Team
In the Connector manual the following is written: "Each instance can synchronize only a CMDBuild class and detail toplevel classes associated to the domains 1:N"
Furthermore in a previous reply you stated "
However, if one of the loaded attributes is a reference attribute then the relation is automatically created"
I cannot see the difference here. The software table is a "slave table" to the hardware table. If this is not the case can you please explain the meaning of your reply and the statement in the manual? I see 2 different answers here. I know the default way to deal with OCS is to use the basic connector, however i only took that as an example, because that's something we have knowledge of. But the principle is the same for my first example.
Or could you give an example of that reference attribute you are talking about?