autonumberhash128 Syn Key issue

[#1]

Hi Guys

I have 3 Synthetic keys on my script load , I have read many posts about how to remove them and whether it actually is important to do so.

I have used some concatenate loads to remove some of them , but I still have these 3 remaining. They are based on fields that I have renamed.

Please see sample of script above,as the Autohash is based on the renamed fields I'm getting an error on the load, can anyone advise a way around this ?

Thanks

A

[ToniKautto]

Try making a preceeding load so that you can use the field names.

Concatenate( MasterTable)

LOAD

     *,

     Autonumberhash128( ... )  as Key1;

LOAD

     //All the stuff you have now besides thre autonumberhash()

[brenner_martina]

Hi,

at first, please post your script, we need to know which fields you have in all the other tables.

2. for what you use the autonumberhash128? you can also concat fields by using "&" like:

Date&'-'&[Assistant Manager]&'-'&Manager As Key1

you don't need to enter here Month, Week and Year!

3. you cannot use fieldnames created by As in the same load-command. use Month(Date) iinstead of Month and so on.

[#4]

Hi Toni/Martina,

I tried to split the load, but as the fields have been named using 'AS' it doesnt recognise them and I still get the error,

Martina, I have pasted in the script below, all the fields that are on the Syntethic keys are created with AS , should I create these in an alternative way so that I may use the Autonumberhash function ?

Thanks

Anne

MasterTable:

LOAD

[brenner_martina]

Hi,

please save the script in the editor  File / Save, than you get a Textfile and upload it here.

[#6]

Hi Martina,

Please find attached

[ToniKautto]

It would be a bit easier to over view if you could attach the QVW file, including the data loaded that creates the synthetic keys. It is also helpfull if you can add a comment int the script for where you are trying to apply the autonumber function.

If the QVW contains sensitive data, please use the scrambling fucntion to make it unreadable;

Settings > Document Settings > Scrambling

Synthetic keys are created when two tables share more than one key value, which creates the need to have an additional table in between to handle all possiblie combinations of these key fields. The simplest way to eliminate a synthetic key is therefor to rename the fields and create a new unique key field.

[#8]

Thanks Toni,

I will post a copy of the viewer, can I just ask is it so horrible to have SYN$ Keys ?

I have loads of charts built around these keys and to be honest if I was to rename them i;m not sure how I would build compartive charts like how I have them now !!!

There seems to be a mixed school of thought on whether the SYN keys are so bad !!!

What do you think ?

[brenner_martina]

Hi, BlossomThe2nd,

can you upload a screenshot of Ctrl+T (Table structure). You concatenate all tables and you have to have only ONE table loaded. There would be no synthetic keys. It would be better if you have for all tables loaded the same number of fileds and the same fieldnames.

And yes, synthetic keys are really horrible!!!!

[#10]

Hi Martina,

I had previously have all the tables concatenated so there was no SYN keys and it was just one table (Mastertable) in the Table structure, but to be honest I didnt really understand the impact of these Syn keys so I reverted back to only concatenating similiar workbooks, so having 4 tables in the table viewer and 3 SYN Keys

From reading the posts I assume I should concatenate all the workbooks to have just one table ?

I