New "Table Contents" Plug-in

[Rich Heilman]

A new plug-in has been uploaded to the trunk directory for "Table
Contents". This plug-in will allow the user to export data from
database tables, and of course import the same. This is a good tool
for sharing demo data across systems. It has been through the first
round of testing and is working good. One known bug is that the
object name F4 help in the export table of SAPlink will result in a
dump, but there are plans to resolve this in the next release of
SAPlink.

Regards,
Rich Heilman

[Eddie Herrmann]

Awesome! I have been waiting for this plugin for a long time. Great
job, Rich.

I added the plugin to the wiki and the plugin download page:
http://code.google.com/p/saplink/wiki/pluginList

Regarding the F4 value help bug, I hope to have this fixed soon. It's
not that hard of a fix, I am just going to add a new method to the
SAPlink root class that does the standard value help, but any plugin,
such as the table contents or BW infocubes, that search a different
way, will be able to redefine the value help method. So far the BW
guys and now you have been asking for this one. Stay tuned...

Cheers,
ewH

[Nicola Fankhauser]

hello rich

great job, and I think this will be very useful for customization tables
with content as well. can your plugin in combination with creating
database tables fill them in the same saplink nugget import operation?
it's the way one would expect it to work, but of course the sequence has
to be 1st create the database table, 2nd insert any data into it.

regards
nicola

[Rich Heilman]

Hello Nicola. We did think about that and it has been decided that
the table contents should always be in a separate nugget. The reason
is that when the tables are created, they are created in an inactive
state, so even if we would try to package them together in a
particular sequence, it wouldn't be activated anyway. I would suggest
that when using, that you have two nuggets, one for all of the source
and objects, and one for your data. So you install all the source,
and then activate all the objects, then go back to SAPlink and update
the tables.

Rich

On Sep 14, 2:18 am, Nicola Fankhauser <nicola.fankhau...@variant.ch>
wrote: