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.
Related
After upgrading in the backend by clicking on update button, I'm getting "Our website is currently undergoing maintenance." both on front- and backend. Deleted update-assets folder, nothing changed. When I go to mydomain/recovery/update/index.php I'm getting:
Slim Application Error
The application could not run because of the following error:
Details
Type: TypeError
Message: trim() expects parameter 1 to be string, bool given
File: .../shop/vendor/shopware/recovery/Update/src/DependencyInjection/Container.php
Line: 41
What can I do?
Delete {shopwareRoot}/files/backup/auto_update/dummy.
Then either retry the web updater or better try and update through shell which is recommended and more reliable.
I finally gave up and installed the shop new.
I had exactly the same problem and i found an evil solution: Simply change line 41 in File: .../shop/vendor/shopware/recovery/Update/src/DependencyInjection/Container.php
from
$version = trim(file_get_contents(UPDATE_ASSET_PATH . \DIRECTORY_SEPARATOR . 'version'));
to
$version = "6.4.18.0";
or whatever version you need.
Hope it helps
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
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.
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
I've created a UDF that accesses the [INFORMATION_SCHEMA].[TABLES] view:
CREATE FUNCTION [dbo].[CountTables]
(
#name sysname
)
RETURNS INT
AS
BEGIN
RETURN
(
SELECT COUNT(*) FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = #name
);
END
Within Visual Studio, the schema and name for the view are both marked with a warning:
SQL71502: Function: [dbo].[CountTables] has an unresolved reference to object [INFORMATION_SCHEMA].[TABLES].
I can still publish the database project without any problems, and the UDF does seem to run correctly. IntelliSense populates the name of the view for me, so it doesn't seem to have a problem with it.
I also tried changing the implementation to use sys.objects instead of this view, but I was given the same warning for this view as well.
How can I resolve this warning?
Add a database reference to master:
Under the project, right-click References.
Select Add database reference....
Select System database.
Ensure master is selected.
Press OK.
Note that it might take a while for VS to update.
In our project, we already have a reference to master, but we had this issue. Here was the error we got:
SQL71502: Procedure: [Schema].[StoredProc1] has an unresolved reference to object [Schema].[Table1].[Property1].
To resolve the reference error, on the table sql file,
right click properties and verify the BuildSettings are set to Build.
Changing it build fixed it.
what Sam said is the best way for doing this.
However, if you have a scenario that you need to deploy the dacpac from a machine that doesn't have that reference in that specific location, you may get into trouble.
Another way is to open your .project file and make sure the following tag has the value of false for the build configuration you are trying to run.
<TreatTSqlWarningsAsErrors>false</TreatTSqlWarningsAsErrors>
This way you don't need to add a reference to your project.
I'm using VS 2019, And even after adding the master db reference still got this issue. Resolved this by Changing the target platform of the DB project as shown in the image below. I had to remove and add back the master db again after this change.