You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have two files. One event file has a key that is numeric of 8 and the lookup file has a foreign key that is 4 alphanumeric. In one view, can we take the 8 char numeric and move it to 4 numeric then to 4 alphanumeric in second column and use that column for a lookup to a file with the value as 4 alphanumeric? Is that allowed in the current version of Geneva? If so, it is something we have the data to test for and I won't fix the data. If not, then I have to fix the reference data.
Need to ask Ian this. He is not currently a member so cannot assign him to monitor this.
The text was updated successfully, but these errors were encountered:
Randall has provided an answer that in the current version of Geneva, it is not possible to reassign a key to another column and then use that in a lookup. We will fix the data.
@bobmcc9 - it makes more sense to have the keys the way you have assigned them - more efficient as numeric. We will change the ref data as I have to upload some of it again anyway. There are only 5 files - don't change your process. Appreciate you got the stuff up there. I will put the layouts here in the issue when I finish them as I have put them in workbench.
Currently we have two files. One event file has a key that is numeric of 8 and the lookup file has a foreign key that is 4 alphanumeric. In one view, can we take the 8 char numeric and move it to 4 numeric then to 4 alphanumeric in second column and use that column for a lookup to a file with the value as 4 alphanumeric? Is that allowed in the current version of Geneva? If so, it is something we have the data to test for and I won't fix the data. If not, then I have to fix the reference data.
Need to ask Ian this. He is not currently a member so cannot assign him to monitor this.
The text was updated successfully, but these errors were encountered: