Anita Whang
My feedback
55 results found
-
4 votes
-
122 votes
An error occurred while saving the comment Anita Whang supported this idea · -
18 votesAnita Whang supported this idea ·
-
14 votesAnita Whang supported this idea ·
-
13 votesAnita Whang supported this idea ·
-
60 votesAnita Whang supported this idea ·
-
71 votesAnita Whang supported this idea ·
-
151 votesAnita Whang supported this idea ·
-
42 votesAnita Whang supported this idea ·
-
93 votesAnita Whang supported this idea ·
-
1 voteAnita Whang shared this idea ·
-
3 votesAnita Whang supported this idea ·
-
3 votesAnita Whang supported this idea ·
-
14 votesAnita Whang supported this idea ·
-
36 votesAnita Whang supported this idea ·
-
137 votesAnita Whang supported this idea ·
-
32 votesAnita Whang supported this idea ·
-
17 votesAnita Whang supported this idea ·
-
32 votesAnita Whang 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.
Anita Whang supported this idea ·
PLEASAE PLEASE PLEASE, LET US GET WHAT WE WANT!