importing invoices in Odoo it throw error always - odoo

when I try to import an excel of provider invoice it always gives the following error in Odoo 13.
"account_move_line" violates the "check" constraint "account_move_line_check_accountable_required_fields
In a new database import correctly, but I need to import it into a database that already has data


From my short research it looks like you need to have accounting fully set up, as this error occurs when all necessary fields and payment journals are not fully set up. Here's a link to a thread on this from the odoo website: https://www.odoo.com/forum/invoicing-5/what-is-the-template-for-customer-invoces-importing-152187

Related

I created a updatesite.nsf from updatesite.ntf template and trying to import a feature

I created a updatesite.nsf from updatesite.ntf template and trying to import a feature and I get an error says "LS2J Error: Java constructor failed to execute in (#304)..." And a long message. Notes and Domino are 12.0.02 both 64 bit...Need help in this . Why am I getting this error ? Nothing in Activity logs either in the updatesite.nsf.
The developer tried to create a JAR and trying to import it the Feature into the updatesite,nsf database and it errors out as above. It should import as I am expecting.

Error message when using UDF and javascript - The project ____ has not enabled BigQuery

In BigQuery console I created a UDF function (language js) and now trying to call it from a saved query. I tried referencing the UDF with projectID.dataset.UDF_Name (same as I am using the for referencing vies/tables). When I click Run in UI I got an error:
"The project XXX has not enabled BigQuery"
I checked the BigQuery API and it says enabled.
When I only used dataset.UDF_Name for reference the query worked but I can save it as view getting another error: Bad routine reference "dataset.UDF_Name()"; routine references in standard SQL views require explicit project IDs
So clearly, the right approach is to use the projectID.dataset.UDF_Name() format but I can't figure out how to get rid of the "The project XXX has not enabled BigQuery" error.
Any help, much appreciated.

Error when trying to create a project under a GitLab group

I just discovered GitLab's groups and decided that it would be ideal for the kind of work I am doing. I created a private group and am getting the following error when I try to create a project under it:
The form contains the following error:
PG::QueryCanceled: ERROR: canceling statement due to statement timeout CONTEXT: while rechecking updated tuple (0,187) in relation "site_statistics" : UPDATE "site_statistics" SET "repositories_count" = "repositories_count"+1
I attempted to do the same in a new subgroup; however, I still get the same error. I must add that I am not using a paid plan of GitLab.
Thank you.

I have the same issue. I think only thing that we can to do is to wait until this error will fix.
Found this issue page: https://gitlab.com/gitlab-org/gitlab-ce/issues/53778

ssis Package validation error ole db source failed

I am getting the following error when I try and run my package. I am new to ssis. Any suggestions. Tahnks
===================================
Package Validation Error (Package Validation Error)
===================================
Error at Data Flow Task [SSIS.Pipeline]: "OLE DB Source" failed validation and returned validation status "VS_NEEDSNEWMETADATA".
Error at Data Flow Task [SSIS.Pipeline]: One or more component failed validation.
Error at Data Flow Task: There were errors during task validation.
(Microsoft.DataTransformationServices.VsIntegration)
Program Location:
at Microsoft.DataTransformationServices.Project.DataTransformationsPackageDebugger.ValidateAndRunDebugger(Int32 flags, IOutputWindow outputWindow, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchDtsPackage(Int32 launchOptions, ProjectItem startupProjItem, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchActivePackage(Int32 launchOptions)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchDtsPackage(Int32 launchOptions, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.Launch(Int32 launchOptions, DataTransformationsProjectConfigurationOptions options)

VS_NEEDSNEWMETADATA shows up when the underlying data behind one of the tasks changes. The fastest solution will probably be to just delete and re-create each element which is throwing an error.

How about disabling validation checks?
Like if you right click on source or destination component and select properties then you will have the property named validateExternalMetadata put that as false and try.
This Solution is working for me.

This normally occurs if there has been a change to your schema, not to stress, just double click on your input and output and it should resolve itself

Make sure your connection is valid. If you are using dynamic connections, then try to set the option "delay validation" = true on the package or dataflow.

In my case destination table structure was not matching with matadata in OLEDB component. I added the missing column which i forgot to add and after that it was fixed.

After researching a bit (check to extract your own conclusions: this and this one), I think I've found a nice workaround for when the problem with the metadata comes from a Ole DB object, but only for a very specific case.
The thing is that when you change your columns names / remove columns / add columns, you can't do anything but update the metadata.
However, if you use a SQL query to retrieve the data from the object, in the case that you don't need to update the query itself, you won't need to update the metadata if the query still can ask for what it wants. Basically, if the query is still valid.
I've tried it within my own ETL, and changed an Ole DB object which was reading the data from an Excel file, targeting one sheet and then I had all the columns selected in the tab.
Changing it for an SQL query to retrieve the full sheet like:
SELECT * FROM ['Sheet_Name$']
Solved completely the case for me, even introducing files with different metadata in headers.

CRM 2013 Importing Action Failure : sdkmessage With Id = [GUID] Does Not Exist

I am trying to import a managed solution that is using Actions.
The import is failing when trying to create the SDK-message. The message is;
sdkmessage With Id = [GUID] Does Not Exist
I've tried re-creating everything but still get the same problem, has anyone had any success doing this?
More details on our problem:
We have exported a solution that contains an "action" workflow and plugin with SdkMessageProcessingStep registered on that action
When importing this solution to another environment, we recieve an error "sdkmessage with Id = Does Not Exist"
The GUID corresponds to SdkMessageId that the SdkMessageProcessingStep is referencing to in customizations.xml.

As far as I know this issue is not resolved yet. You can vote on Connect.

I assume you have this problem after installing rollup update 1 for SP1. When I installed RU1 and try to import solutions, I got the same error. This can be resolved by updating the organization. Goto deployment manager and select the organization and click Update. This will update the guid's and then the solution imports successfully.