jBoss Business Central Error Message when Opening Assets - jboss

To all
When trying to open an asset (DRL or Legency Test), I receive the message "Unable to complete your request. The following exception occurred: name is empty."
I can't find any hint what this means. My rules import from different projects which all can be accessed.
Does anybody have an idea what this could mean? Thank you very much already in advance.
big hug
Michael

I found out by myself. The external data objects configuration had an empty entry. So be careful when adding an external data object - you are able to add an empty row and Business Central let's you save this ... with the empty row causing the error described.
happy coding
Michael Lutz

Related

How to resolve TinyButStrong's 'at least one tag corresponding to w:tr is not found' error?

I'm creating a project to mail merge a given .odt file and provide a .odt output. When i'm performing the mail merge operation it provides me this error
TinyButStrong Error in block's definition [CiviCRM.display_name...]: at least one tag corresponding to w:tr is not found. Check opening tags, closing tags and embedding levels.
Myfilecontent.odt
[CRM. display_name;block=w:tr]
Date: 2/3/2020
Dear [CRM.postal_greeting;block=w:tr],
Thank you for joining the event...
I have no idea how to resolve this. could someone help me to solve it?
Thanks in advance!
Update
After i replaced w:tr with tbs:row, still I'm receiving a similar error
TinyButStrong Error in block's definition [CRM.display_name...]: at
least one tag corresponding to tbs:row is not found. Check opening
tags, closing tags and embedding levels.
w:tr is an XML entity for Ms Word , not ODT.
You should use the alias block=tbs:row so that its is format independent.

"General system exception happened" always while importing product csb magento2

Magento2 shows "General system exception happened" always while i am importing CSV, while some time before its gets accepted by magneto. Currently some product attribute incresed.
Try to save the CSV with open office by checking option of quote every field with double inverted commas. This helped me to solve this. Hope will solve your problem as well.

Extbase, Uncaught TYPO3 Exception. Flush system cache solves is for a while

Site works fine. Suddenly it will through an error. When clicking "flush system cahce" the error will go away for a some time. Anything from minuttes to severaƦ hours.
Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1247602160:
Unknown column 'tx_my_domain_model_formular.rel_formular' in 'where
clause' |
TYPO3\CMS\Extbase\Persistence\Generic\Storage\Exception\SqlErrorException
thrown in file
/webserver/typo3/src/6.2.15/typo3/sysext/extbase/Classes/Persistence/Generic/Storage/Typo3DbBackend.php
in line 862.
It is correct that the columns does not exist. But how to preceed in finding the error after this? Where is the sql generated that causes the site to crash?
UPDATE
A check "myParentObj->getChildObj instanceof myChildObjClass" used to work just fine. After changing myParent model to lazy load the ChildObj, then the class of childObj changed from childObjClass to a lazyLoadClass... I am not sure but I guess that is in turns somewhere somehow caused the core error seen in the log.
How to investigate further I simply cannot work out. Eg. store all DB calls in a file og DB to analyze after the error occours.
First
Please take time to write a good question. For a good question you'll get a good answer. It doesn't have to be perfect (not everyone is a native english speaker) but please reread your question.
Answer
If all fields are defined correctly, just run a DB compare from within the installtool.
If not, you need to define the DB-fields in your extension correctly.
Is this your own extension? When doing the query that triggers the error you could call execute(true) to generate the actual SQL statement and debug from there.

0x80048470 - Importing CRM Solution

I am trying to import an unmanaged solution but for some reason I am getting the following error:
Failure: 0x80048470 - The entity relationship role of the referencing entity is required when creating a new one-to-many entity relationship business_unit_new_contract.
It's interesting because I've opened the costumizations.xml and the relationship is there. Also, when I look up at the exported solution entity that has the relationship, the relationship is also displayed.
At first, I was receiving an 0x8004803A error as shown:
Failure: 0x8004803A - The import has failed because component of type 50 is not declared in the solution file as a root component. To fix this, import again using the XML file that was generated when you exported the solution.
So, I opened the solution.xml and added a new for that particular type, which was not in the file.
Has anyone ever experienced that? Also, This relationship shown is between businessunit and one of my entities.
Is there any way of fixing it through database? What would be the best solution?
Thanks in advance,
Dem
I'll just try to explain your second problem (0x8004803A), since it happened to me today.
By the way, this was one of the few times when 'Download log' was actually helpful (it contained the real error).
The import has failed because component of type 50 is not declared in the solution file as a root component.
Entity type code 50 apparently stands for (global) Application Ribbon. This can happen when manually adding the <RibbonXmlDiff /> section to customizations.xml. If this happens it is enough to add following line to solution.xml:
<RootComponents>
...
<RootComponent type="50" schemaName=":RibbonDiffXml" />
</RootComponents>

Error showing at tAccessInput component

While using tAccessInput component in my job, it showing error like,
It may not be a database that your application recognizes, or the file may be corrupt.
But, it all the connections and database/table names are valid in my job.
What can be the problem. and how can i resolve it.
Metioning the exact DBVersion is more important for tAccessInput/tAccessOutput.
Like Access 2003/Access 2007 and associated database file name.