Hello,
When I try to send approval request it is giving me error that User xxx doesn't exist in User Setup table.
Then I went to code and I found out this in codeunit 439.
How could this ever can be possible? (Right me if I am wrong).
And it is default code.
UserSetup.SETRANGE("User ID",UserSetup."Approver ID");
IF NOT UserSetup.FIND('-') THEN
ERROR(Text005,USERID);
And now what shall I do get rid of the error?!
Thanks,
Amaraa
Answers
"Never memorize what you can easily find in a book".....Or Mibuso
My Blog
I have setup the user in User Setup table.
However, the system gives me the error.
So, that's why I needed to go to the code. (Sorry for the brief introduction).
EDIT: the easiest solution to check the value is to change this to
"Never memorize what you can easily find in a book".....Or Mibuso
My Blog
it's not common to use a value of a field of the table we're filtering as a filter value, but it's useful sometimes...i think that it is used to group records with the same user id field, but i've never took a deep look at this codeunit...
and what about your problem?did you solve it?
"Never memorize what you can easily find in a book".....Or Mibuso
My Blog
the error tells you that USERID does not exists, but the check is done with a value of a field in a table, not on the USERID...you should try to change the error text as i told you and check if the user does exist
"Never memorize what you can easily find in a book".....Or Mibuso
My Blog
"Never memorize what you can easily find in a book".....Or Mibuso
My Blog
Thanks
If a user has the the checkmark in Unlimited approval, the search terminates (the Amount Approval Limit field is ignored in this case).
Since, without setting the checkmark, you still got the error some user does not exist, and from what you write you think the user is there, you probaby did not make the correction Belias proposed: This code change actually tells you, which user setup record is missing. The original code simply is wrong.
You should set up approvals in such a way that (only) the last approver in the chain has unlimited Amount approval limit. All the others (starting with the user itself) should (sensibly) be configured with a strictly accending approval amount.
the best solution is your answer below:
You should set up approvals in such a way that (only) the last approver in the chain has unlimited Amount approval limit. All the others (starting with the user itself) should (sensibly) be configured with a strictly accending approval amount.
Best regards.