Maybe I'm missing something, but could you not simply name the output attribute the same as the primary key column?

Protip: you can also generate a UUID within most transformers using @UUID(), e.g.

I guess i was thinking of this transformer. Creates the GFID for me.

The GUIDGenerator custom transformer is not needed, you can get the exact same result from a simple AttributeCreator and it allows you to specify the output attribute, e.g.

sorry we may be thinking two different things here. I create the column and populate it just fine. What i want is for it to auto assign the column as a primary key in the index column under user attributes.

or just...

Has anyone been able to solve this? This solution doesn't help me. What we need to be able to do is assign the primary key so that we can use automatic and dynamic attributes. Manual defeats the purpose.

Perhaps consider posting it as a new question, you'll get much better visibility and it'll be easier for others to help out. The more details you can supply about why the options below don't work for you, the better.

Yes, probably a good idea to repost although I have seen this same topic several time, simply the issue is assigning the primary key constraint. The column is already populated but when importing into the database the column doesn't have primary assigned. I need to keep the writer attributes definition as automatic. When drop and create the data is requiring this assigned but I have dozens that drop and create with new schemas almost daily and I can't assign it manually.