Nancy Terriquez
My feedback
156 results found
-
10 votesNancy Terriquez supported this idea ·
-
41 votesNancy Terriquez supported this idea ·
-
14 votesNancy Terriquez supported this idea ·
-
16 votesNancy Terriquez supported this idea ·
-
171 votesNancy Terriquez supported this idea ·
-
13 votesNancy Terriquez supported this idea ·
-
14 votesNancy Terriquez supported this idea ·
-
25 votesNancy Terriquez supported this idea ·
-
10 votesNancy Terriquez supported this idea ·
-
41 votesNancy Terriquez supported this idea ·
-
8 votesNancy Terriquez supported this idea ·
-
16 votesNancy Terriquez supported this idea ·
-
39 votesNancy Terriquez supported this idea ·
-
32 votesNancy Terriquez supported this idea ·
-
20 votesNancy Terriquez supported this idea ·
-
130 votesNancy Terriquez supported this idea ·
-
15 votes
This is a CALPADS bug on their end. They DO intend to allow these special characters again, so we will not be changing our process at this time. If the
SINF update is needed, the customer either needs to make it manually in OM, or remove the offending characters from Aeries, but ALSO delete the CALPADS log entries for that change (the ones that contain the offending characters) so they won't be extracted also.
Nancy Terriquez supported this idea · -
47 votesNancy Terriquez supported this idea ·
-
38 votesNancy Terriquez supported this idea ·
-
73 votesNancy Terriquez supported this idea ·