KB-Entries 20.3.1: Unterschied zwischen den Versionen

Aus firesys Hilfe
Zur Navigation springen Zur Suche springen
Keine Bearbeitungszusammenfassung
Keine Bearbeitungszusammenfassung
Zeile 18: Zeile 18:
}}
}}
-->
-->
{{
Vorlage:KB-EintragSpalte
|Modulbild=KB-Pfeil.png 
|TitelKB=Differing XBRL settings between master/story impeded synchronization
|ModulKB=linkdocuments
|ProgrammKB=Word
|TextKB=Because of differing XBRL settings, the story could not be updated, and the master could not be written back. Starting with version 20.3.0, it is possible to synchronize anyway and to select which settings are taken over.
}}




Zeile 69: Zeile 60:
|ProgrammKB=Word
|ProgrammKB=Word
|TextKB=It happened that the change mode of a story could neither be activated nor deactivated. This bug was fixed in version 20.3.1.
|TextKB=It happened that the change mode of a story could neither be activated nor deactivated. This bug was fixed in version 20.3.1.
}}
{{
Vorlage:KB-EintragSpalte
|Modulbild=KB-Pfeil.png 
|TitelKB=Differing XBRL settings between master/story impeded synchronization
|ModulKB=linkdocuments
|ProgrammKB=Word
|TextKB=Because of differing XBRL settings, the story could not be updated, and the master could not be written back. Starting with version 20.3.0, it is possible to synchronize anyway and to select which settings are taken over.
}}
}}



Version vom 7. Januar 2021, 12:30 Uhr

New Features

Failed Data import shows incorrect rows
KB-Pfeil.png
Toolsvalidation.png | Excel.png
If structural problems occur during import into the Meeting Point, the rows in which these problems occurred are now displayed as well.


Bugfixes

TeamViewer could not be started from Word/Excel
KB-Pfeil.png
Firestarter.png | Word.png
An error regarding QuickJoin and QuickSupport has been fixed so that it is now possible to connect to TeamViewer from Word/Excel again.


Cell highlights could only be set on column highlights
KB-Pfeil.png
Layouttables.png | Excel.png
There was the bug that cell highlights could only be set where column highlights were already present. Now these functions are independent of each other again.


Change mode of the story defective
KB-Pfeil.png
Linkdocuments.png | Word.png
It happened that the change mode of a story could neither be activated nor deactivated. This bug was fixed in version 20.3.1.


Differing XBRL settings between master/story impeded synchronization
KB-Pfeil.png
Linkdocuments.png | Word.png
Because of differing XBRL settings, the story could not be updated, and the master could not be written back. Starting with version 20.3.0, it is possible to synchronize anyway and to select which settings are taken over.


Data import was performed with the "Edit" button grayed out
KB-Pfeil.png
Toolsvalidation.png | Excel.png
File import into the Meeting Point could result in selected imports not being able to be edited afterwards. This error has been fixed.


Sorting and displaying key dates when creating an automated worksheet
KB-Pfeil.png
Toolsvalidation.png | Excel.png
When creating an automated worksheet, each key date in the Table Manager was automatically filled with the latest available date of the account group up to now. Now, however, they are displayed in ascending order and can also be entered manually in ascending order.


Edit failed Data import showed empty list
KB-Pfeil.png
Toolsvalidation.png | Excel.png
If there were structural problems when importing data into the Meeting Point, and the data should be edited afterwards, an empty list could appear in the file settings. This error was fixed in version 20.3.1.


Wrong number format accepted for Data import into the Meeting Point
KB-Pfeil.png
Toolsvalidation.png | Excel.png
If an incorrect number format was specified in the Import definitions, an import could still be performed by mistake. Starting with version 20.3.1, an error is now displayed.


Cell highlights could only be set on column highlights
KB-Pfeil.png
Toolsvalidation.png | Excel.png
A CSV file in which a column header contains both letters and numbers, could not be imported into the Meeting Point via Data import by mistake.


Error message about duplicate tags not logical
KB-Pfeil.png
Toolsxbrl.png | Word.png
If an already existing tag was reassigned, the error message erroneously did not show the position where the tag was already assigned, but the current position. Now the tag refers back to the previous assignment.


Empty rows in double-sided tables resulted in unequal number of rows
KB-Pfeil.png
Toolsxbrl.png | Word.png
Empty rows in double-sided tables were hidden in the tagger, so that the left and right sides did not have the same number of rows. As a result, the individual rows were not correctly assigned to each other. This problem has been solved by always showing all cells in double-sided tables.


Tags were lost during save/close/open
KB-Pfeil.png
Toolsxbrl.png | Word.png
After saving and reopening, tags on the second page of double-sided tables were lost. To work around this error, it may be necessary to reset the tags.


Error message during iXBRL export
KB-Pfeil.png
Toolsxbrl.png | Word.png
An error in text tags caused the tag to be considered incorrect in the check. Thus, an error-free iXBRL could not be created.


Empty cells caused an error in the calculation
KB-Pfeil.png
Toolsxbrl.png | Word.png
If one of the cells within the calculation was empty when creating a calculation, a neighboring cell has been included in the calculation.


Mixed Tags in Calculation generated validation error
KB-Pfeil.png
Toolsxbrl.png | Word.png
Duration and Instant Tags must not be mixed in a calculation, otherwise they will generate an error. There is now a rule that intercepts the mixing.


Period was not recognized correctly
KB-Pfeil.png
Toolsxbrl.png | Word.png
End and start date of the billing period were not recognized correctly. This error has been fixed.



See also

Navigation hoch.svg The firesys Knowledge Base
Navigation links.svg The new features of version 20.3.0
Navigation rechts.svg The new features of version 20.3.2

Further contents

firesys website
Customer area
YouTube