WebCOBRA.com Community Message Boards

cgomez
Posts: 18
Since: 02/22/2008

I need to know what the table structure are to help build the XML feeds into WebCobra. We know some of the fields that we can load, but what are max lengths or values that can be store on the XML. We are building the table structure here in order to build the XML file. Each table would be related to each element on the XML file. For now I just need the QB tables structure and relationship between each other. I also need to know the values that are acceptable and lengths. The example on the website only shows a few fields and we are already notice a field difference between the CSV file and XML File.

jwolgamott
Posts: 257
Since: 09/26/2005

When you say "table structure" -- what database are you referring to? Is this TravisCobra, or another system that you are converting from?

The CSV and XML are indeed different; the CSV is intended to bring over information easily and matches the TravisCobra import file format.

cgomez
Posts: 18
Since: 02/22/2008

This for WebCobra. I am converting from a system called "Cobra Solutions" to WebCobra. I am having to use the XML file, because I was told that was only way to populate the UserDefinedKey to a person. I am loading history into the system, so I keep running into issue because of fields that are missing from the example that I can use. Now if I had some documentation on what fields are in each element that would be what we are looking for. You list the elements in the "Edit Example" section, but to what fields are available is missing. The table structure in question is the elements in the XML file. In order for us, to export this information to you each element has to be put into a table, so we were just asking the fields to correctly setup these tables.

jwolgamott
Posts: 257
Since: 09/26/2005

OK, I've got a better understanding of the background of what you're trying to accomplish.

Here's some resources to help you out:

- In IT Resources in WebCOBRA, there is a dictionary... It contains an explanation of the IDs that you'll need to use when importing a QB, like Event Codes (termination vs divorce, etc), and Date Types, like QB Created and Paid Through date.

Our customers have had success with importing the Company structure (Companies, Insurance Carriers, Benefit Plans) with the XML file, and then using the simpler CSV file for QB creation.

The complete listing of fields in the XML file is found in the "XML Format - Download the XML Format shell" link --- it should give you a head start.

cgomez
Posts: 18
Since: 02/22/2008

We saw the dictionary, but for example the QB Date Type Codes are in the dictionary and not in the example. I have learned recently about the QBDateTracking element which is not in the examples or in the XML Structure layout this in the same section. With that there is any documentation on how the fields are used or what effect they will have when applied. Is there anything that will explain the XML structure and what fields do. Another thing that was asked is the limit size or type on the fields within the elements. What is the limit size for the QBID in the QB element. Can I put a variable size of 1000 or is 50 the max size I can use. We learned that the dates will not accept slashes, but using dashes in the date worked. If we knew that ahead of time, it would of saved us time on programming.

jwolgamott
Posts: 257
Since: 09/26/2005

You'll want to use the DateTracking node that is a child of the QB Groups element to track dates -- its in the XML Format, but I agree that it could use some documentation as to its purpose.

For QBID -- the max length for QBID is 255 characters.

You can safely assume that the max length for strings is 255 characters, and for Codes (Company Code, Plan Code), the max is
9 characters.