Notifications
Clear all
Topic starter
I'm getting the error "ERROR: 32848 BAD VALUE OR BAD INDEX" whenever I try to send a flag to a particular user using MEL_SEND_FLAG(). I've used this function many times in the past, but we hired a new person to receive these flags, and it just won't send to them. Is there articular security access the user needs for this not to error out?
Posted : June 18, 2014 3:48 am
Under Centricity EMR 9.5, Privileges show the users settings for their permissions.
Not sure where this would be found under higher versions of Centricity.
"Go / Setup / Privileges"
Check under your users Privileges, Look at their "Alerts/Flags" and see how these are set.
Also look under
"Go / Setup / Preferences"
Desktop
Alerts/Flags
Posted : June 18, 2014 6:30 am
Topic starter
I've been testing for a while now. I have given this particular user access to all the items under Alerts/Flags without any luck. I can see why it wouldn't really have anything to do with this because they all have to do with "other users' flags." I'm starting to wonder if this might be a bug with CPS 12.0.3.1383.
Posted : June 18, 2014 6:35 am
I have a test database with 12.0.3.1383 (we are currently on 12.0.0) and i tried a few MEL_SEND_FLAG functions we have been using since CPS10 and they work just fine
Posted : June 18, 2014 10:51 pm
Topic starter
Yeah, it's pretty strange. These seem to be CPS Read Only security access users, but when I switch them to nurse or something else, they still don't work. I'm going to try recreating the user account and maybe start off with different security access.
Posted : June 18, 2014 10:57 pm
I know this is a very old thread but I came across this exact issue recently and wanted to share the fix that we had found as it is very unintuitive.
As a bit of background: we have a run process button that sends flags to multiple users and buckets based on what was filled out during the visit. The code had worked for all users until late last week, and still did work for all of the other users/buckets except for this one. The fix turned out to be related to the PW. I had to reset the bucket PW, sign in as the bucket with the new PW, and then the form was able to send the flag to the user again.
As for root cause as to why this was the issue, I am unsure. But resetting the PW and signing in as the bucket ended up fixing the issue.
Thanks,
Mike
Posted : July 10, 2017 11:13 pm
