Difference between revisions of "Duplicate Enumvalue"
From IMSMA Wiki
Line 7: | Line 7: | ||
imsmaenum.enumcategory, | imsmaenum.enumcategory, | ||
imsmaenum.enumvalue, | imsmaenum.enumvalue, | ||
− | COUNT (imsmaenum.imsmaenum_guid) | + | COUNT(imsmaenum.imsmaenum_guid) |
FROM | FROM | ||
imsmaenum | imsmaenum | ||
Line 14: | Line 14: | ||
imsmaenum.enumvalue | imsmaenum.enumvalue | ||
HAVING | HAVING | ||
− | COUNT ( | + | COUNT(imsmaenum.imsmaenum_guid) > 1 |
− | |||
− | |||
ORDER BY | ORDER BY | ||
imsmaenum.enumcategory ASC, | imsmaenum.enumcategory ASC, |
Revision as of 11:13, 13 July 2014
Duplicate enumvalues will cause import problems that are difficult to detect because there is no error message. |
The import problem will also occur in cases where one enumvalue is active and the others are inactive. The import problem does not apply to CDFs. |
If this SQL gives a result set, contact your GICHD IM advisor:
SELECT imsmaenum.enumcategory, imsmaenum.enumvalue, COUNT(imsmaenum.imsmaenum_guid) FROM imsmaenum GROUP BY imsmaenum.enumcategory, imsmaenum.enumvalue HAVING COUNT(imsmaenum.imsmaenum_guid) > 1 ORDER BY imsmaenum.enumcategory ASC, imsmaenum.enumvalue ASC