Our company is currently using Odoo 12 and we are getting this validation error in a couple of different modules. When completing the final stage and only the final stage of a Manufacturing Order we receive this error in the picture below. The error also appears when trying to register a payment from an invoice. It seems to be thrown because an invoice or order is being finished and needs to change statuses but it only appears to be the final status change where we have the issue. Has anyone else run into this or could it be coming from some type of module setting?
odoo error screenshot
It can be hard to tell because it could be due to a routing issue which is tricky. I would search for all related records and see if anything else needs the record. Also, check your routing for the MO. It could be that you can't validate a MO due to another record needing to be processed first.
Related
I have been struggling for days now trying to get my Firestore security rules to work with basic rules - even ones copied and pasted from the docs. I have tried to spin up the development and test emulator, but it failed due to what appears to be npm conflicts.
I tried to use the rules playground, but it gives me the error that the "get" function is not recognized. I found that this problem has occurred in the past. I could really use some help in figuring out where to start with this. I am considering abandoning the firestore system all together as along with these problems, the system frequently fails to connect.
The full get statement is ...
get(/databases/$(database)/documents/users/$(request.auth.uid)).data.designer ==true
I have tried a number of variations of this with no success.
If this is a problem with the tester, how can I test my queries and figure out where the problems lie. If this is a bigger problem, what do I do?
Update : The read will work if I am querying the users collection as in the query below.
allow read : if get(/databases/$(database)/documents/users/$(request.auth.uid)).data.designer == true
The issue seems to lie in when I need to retrieve docs without knowing the specific ID of the doc in question - getting multiple docs based upon the security rule.
You are testing without a signed in user, which means that the $(request.auth.uid) expression inside your call to get() fails. To make this work you'll need a signed in user.
I'm currently experiencing something rather weird: while migrating emails from a GoDaddy email server to a new G Suite set up for a number of users, I was able to successfully move for a couple of emails, as confirmed by Google's 'Complete' tick beside them. I was able to observe the migration too as it went on.
However, for one of the emails, the number of emails read just seems to keep increasing, and it still hasn't displayed 'Complete', but remains stuck on '99%'.
See screenshots I literally took just now below: as of the first latest screenshot, it says 'Successfully migrated 3230 emails', while stuck on 99%:
Then I hit refresh, check the status of that same account, and now it says '...3250 emails', while still stuck on 99%:
This isn't how it's supposed to behave, at least that isn't the behaviour I experienced with the previous 4 emails in that list. Ideally, it should say 'Migrating X out of fixed_amount emails'. In this case, that fixed_amount was
about 2,000 emails. It has now since passed that figure, but instead of showing 'Complete', it instead shows 'Successfully migrated new_amount' where new_amount keeps increasing.
This has been ongoing for almost 24 hours now. Honestly, I don't know if this is a bug or not. I really just need some helpful info to know if I should be concerned or not, perhaps maybe if someone else has run into this. Anyone?
Stumbled on to Google's documentation: https://support.google.com/a/answer/7032598?hl=en
To quote the 'Why does my migration look like it's stuck at 99%?' section:
You’ll see 99% when all email is migrated. After everything is
migrated, the data migration service applies any labels to the
migrated email, which can take time. When the labels are applied, you
should see that the migration is complete (100%).
You might also see this issue if the estimated number of emails to
migrate exceeds the actual number of messages. The migration will
report 99% until the migration completes. This process might take some
time.
You shouldn't be concerned. I was migrating around 29.000 emails from a personal gmail to Google Workspace gmail and the migration took 4 days (migrating only one user), from which the last 1.5 days the migration was "stuck" at 99%. No need to restart the migration, eventually it indeed finishes. I also got several error codes (e.g. 17009 - 'Generating an access token with the supplied credentials was unsuccessful...'), but none proved valid, I haven't actioned on them as, like in your case, I saw the number of migrated emails increasing.
I have an assignment where before I get a message from a server and tweet it, I have to check if an error occurs. If it does, it says that I have to "show with a human task an error message specifying a number and the error received. After that, the process ends".
In another part of the workflow I do check for errors but I'm not required to show anything, and frankly I do not understand how that would work, I believe my mistake is that I might be thinking too literally or too close to code showing errors and such.
Any help or place to look for information?
The answer to this question will vary depending on the edition of Bonita BPM that you are using.
With Community edition:
Note that error management will impact process design.
You can implement the following scenario:
retrieve the error (this can be done by using a custom connector output).
store the error details in a process variable.
have an exclusive gateway with a condition that branches to an optional human task that shows the error in a form.
With Performance edition:
There is a built in error management feature in Bonita BPM Portal. As an administrator you may review stack traces associated to connector execution failures, edit some settings and replay the connectors.
All of this is done without impacting the process design.
We are a small school district and I have written a simple form for teachers to report disciplinary problems. The destination spreadsheet has a script bound to it and an onFormSubmit trigger is set.
The script uses the form data using the event object e from the function onFormSubmit(), creates a report in Google Docs, send email notices to relevant people and does a few maintenance tasks. Link to code.
It's been working fine until recently when the trigger occasionally fails to fire. No error message; the form data is submitted. This morning, two teachers in separate incidents entered a form and the trigger failed; a third entered the form and it worked.
The form and sheet are 'owned' by the Dean of Students account and users access the form anonymously on the network (not in Google account). The form is set with VIEW privilege for anyone with a link; the sheet has no privileges, only owner.
I am completely stumped as to why this would work sometimes and not others. Clues?
I recently developed a Google Spreadsheet with multiple sheets that takes data from 4 different forms. When the form data comes in, I have scripts that run multiple calculations and formatting on that data, so the onFormSubmit trigger is crucial for me. I've come across the exact same problem you are having right now.
At first I thought there was something wrong with my code and I checked it over and over again. Then, I scoured the web for answers to why my triggers failed about 10 to 20% of the time. A lot of what I found on Google forums related to problems from Google's side. I found that tons of people faced the same problem I had, but none of them had a definitive fix.
My eventual solution was to create yet another trigger that fires every 8 hours. This runs everything my other triggers run yet again just to make sure everything I wanted to do has been done. Of course, that trigger could fail, too. But so far, I've been checking the sheet (new data comes in about every 6 hours or so) and I haven't had to fix any problems whereas before, I had to rerun scripts daily.
Maybe for your case, you can have a function that goes through and sends emails that previous faulty triggers failed to send. Then have this function fire every however many hours you prefer.
This is probably not a very satisfying answer but it's the best I can do. Good luck!
I have a report in SSRS with "Data-driven Subscription" , but sometimes there is errors like below
Done: 10 processed of 10 total; 10 errors.
and the reason of these errors I think network problems, ssrs can't store pdf in the network folder.
So I need a way to handle any error that happened in this stage to be able to retry again, or at least to know witch reports not generated correctly,
any Idea how can I handle these errors?
There is no technique to error capture, you just have to carefully adjust the paremeters if you have them in the report.
I have many years experience in making these statements, and in the beginning I had a similar problem but I solved it