I would like to follow up on this.
Backups retain table information and SQL data. Import retain just the object definitions without any data, which is why the table is not "exported" (It's definitions are but it will not be created).
There are several options to go with this:
1) As mentioned above by Michael - Create a data source to fill this table (As shown during insight) and plug it as a CSV file.
2) Create a DB based data source, but in the cache query don’t select from a source but rather hard code the info. Here’s what you need to do:
* Create a data source type for mysql on localhost and use wfa/Wfa123 for credentials
* Create a dictionary entry for your object.
* Create a cache query to cache into that object type, but don’t select from the database, just use static info. Here’s an eample:
SELECT
'1', 'TLV', '10.68.128.245', 'netapp',
UNION
SELECT
'2', 'ATT', 'vcloudapi.g218406.synaptic.att.com', '107945'
UNION
SELECT
'3', 'Belgacom', 'vcontainer-demo.belbone.be', 'Customer7'
That would create 3 lines in the target table.
Just create a data source from this data source type and run acquire once manually. The table would be fully populated.
That solution would be fully exportable in one shot without added files.
Cheers,
Yaron