ClientVisitGUID field: Difference between revisions
Ttenbergen (talk | contribs) No edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 14: | Line 14: | ||
One advantage would be that ClientVisitGUID remains the same even when other data is corrected for a John Doe. One disadvantage is that not all our profiles are entered from Cognos, and this field would be blank for those that are not. Collectors can't look the field up in EPR, so it would have to come from Cognos data. | One advantage would be that ClientVisitGUID remains the same even when other data is corrected for a John Doe. One disadvantage is that not all our profiles are entered from Cognos, and this field would be blank for those that are not. Collectors can't look the field up in EPR, so it would have to come from Cognos data. | ||
== Blank CliendVisitGUIDs == | |||
The same scenarios as [[ClientGUID field#Concerns]] could lead to missing lines here. | |||
== Log == | == Log == | ||