tx PMC export Table Extension with CDF

OmeLuuk · #1 7th August 2023, 14:16

Just wondering...
By design it seems not to be possible to create a PMC solution on checkin or commit of an extension (as is in LN Studio). Or do I have to set the "Integration with PMC" checkbox on the used activity?

Then when creating a PMC dump for a table extension manually, I only add the table extension DLL txest<table>. I noticed that in the PMC dump header no mention of the CDF fields are present..? So when and how are the CDF fields (records in ttadv491, ttadv492, ttadv493) included in the PMC solution?

RieseUSA · #2 8th August 2023, 01:40

The ability to include CDF fields with a table extension got introduced with the LN 10.7 tools. You just need to include the library for the table extension and the CDF data will be included. There is no mentioning of the CDF data with the solution.

I have done this by manually creating a PMC solution and also via the automatic generation when using LN Studio and with the Integration with PMC option.

If you are using LN 10.7 tools and this does not work, e.g., the CDF fields do not end up on the target system, I believe there is some PMC version setting to allow creating solutions for a target system that does not have the LN 10.7 tools. If that is set to an earlier release, I expect that the CDF data will not get included.

OmeLuuk · #3 8th August 2023, 12:29

Quote:

Originally Posted by RieseUSA

You just need to include the library for the table extension and the CDF data will be included. There is no mentioning of the CDF data with the solution.

I know it works, but was just wondering how. I think they must be included in the encapsulated ttiex dump, but not mentioned in the PMC header. What I did not do (yet) was extract the ttiex dump...

OmeLuuk · #4 10th August 2023, 17:58

Today we saw that a table extension that was imported with PMC (and contained CDF fields) brought in a CDF field on a table. But after deactivating the extension and even removing it entirely, the table extension (ttadv491) is stil present...

andreas.toepper · #5 11th August 2023, 08:09

Yes that's true. And I think it's OK. A new CDF in a table is activsted by a convert to runtime datadictionary (c2rtdd) run. To disable it, LN would require to remove the field from the table with a data loss. So I think i's ok, when you disable a table extension that the CDFs are still present in the table.

That a CDF is not removed by c2rtdd after uninstalling a solution is somewhat strange. I never tried that.

JaapJD · #6 11th August 2023, 12:19

Quote:

That a CDF is not removed by c2rtdd after uninstalling a solution is somewhat strange.

OmeLuuk is not talking about uninstallation the solution, but about removing the extension. That will indeed not remove the CDF, but uninstalling the solution will do it.

OmeLuuk · #7 14th August 2023, 11:31

Quote:

Originally Posted by JaapJD

... That will indeed not remove the CDF, ...

But that will obscure the current table status somewhat. You will have to go to the Customer Defined Fields menu under Application Configuration to maintain these fields.
As for the table extension itself, deleting it is an obvious choice when there is no logic involved (no hook implementation).

Maybe it would help a bit when the existence of the CDF fields is shown in the menu of Extended Components under the menu on the left hand side in the Extension Modeler.

OmeLuuk · #8 24th August 2023, 16:57

Quote:

Originally Posted by JaapJD

... removing the extension. That will indeed not remove the CDF, ...

By design, you should add the CDF by extension, but once set up (even on the source system for the PMC solution) the link with the extension is not so that removing the table extension will also remove the CDF fields. As by functionality it makes sense, but it feels not right that once a CDF is in place, you could add it to a session in LN Studio, but not in the BW/DFE fashion. Is it intentional that the table extension may be deleted when a CDF for the table is defined?