EN - Release notes version 1.8.3.5





Changes

Import and export

  • PIM-4577: The Excel export functionality via the front-end gave an error message if a user had insufficient rights to related tables. This has now been adjusted so that an error message no longer occurs.

  • PIM-4534: Clicking on the message box caused a fatal error message due to incorrect export files. An adjustment has been made to prevent this crash from occurring again.

  • PIM-4402: Exporting data to Excel (via the front-end) was very slow if user group filters were active in a domain. The performance of this has improved considerably.

  • PIM-4437: Importing files has been completely rewritten in this version. This was necessary to guarantee the stability and performance of the import. In addition, this is simplified in terms of code, making it easier to maintain in the future.

  • PIM-4428: It is made possible to also import incoming relations when importing files. An example is that an image (which is created in a separate table) can now be directly linked to an item.

  • PIM-4228: When importing files (like images) it was previously not possible to fill attributes via a standard / fixed value. This is made possible in this release.

  • PIM-4295: When importing files, it has been made possible to use conversions. An example is that a field is filled with a fixed value, or that a string conversion is performed in which a value is translated into another value in the import.

  • PIM-4464: From this version there is only one option to import files into Beeyond, and that is by choosing for the indicator type 'Attachments' in an importmapping. This import option also supports the old functionalies, and simplifies the maintenance of Beeyond. All "old" mappings are automatically migrated.

  • PIM-3440: A possibility has been added to the import that determines whether a field in Beeyond should be cleared if the field in the import file is offered empty. We regularly see the fact that suppliers only offer mutations of data. This option makes it possible to correctly process these mutations, whereby no data is deleted in Beeyond if it is not supplied. In addition, this setting ensures that if an import mapping refers to a non-existent column name (for example due to a typing error), this attribute is not emptied everywhere.



  • PIM-4220: This is a continuation of the previous issue (PIM-3440). It has been ensured through this that the option 'Clear value when empty' can be applied to all attribute types, and not only for string attributes.

  • PIM-3959: On the acceptance environment of Beeyond it is made possible to import files from the FTP (such as images). The images are of course not deleted from the FTP if they are imported.

Printwizard

  • PIM-4553: In the print wizard the column name 'Select number of copies' has been changed to 'Amount'.

  • PIM-4469: The print wizard has been simplified. Previously 4 steps had to be followed (1. Overview, 2. Select template, 3. Select number of copies, 4. Overview), this is now simplified to just one step in which the desired numbers can be entered directly.

  • PIM-4227:The print module makes it possible to print customer cards from Beeyond. An adjustment has been made to make this process more efficient.

  • PIM-4552: In the layout of the printing it is made possible to select incoming relations in the template file. This makes it possible, for example, to print a customer card directly from a contact person, whereby customer data is also printed on this customer card.

  • PIM-4544: The print icon for printing a main record (for example, customer) was different from the print icon for relations (for example, customer contact). This is now the same.

Other changes

  • PIM-3852: Indexing of messages via the User Group Filter has been optimized. This background process is now more efficient, with the result that data is faster accessible in Beeyond.

  • PIM-4549: A URL can be entered in attributes of the 'External source' type. In this version an adjustment has been made that https: // is automatically added to the URL if it is not entered.

  • PIM-4138: If an incorrect URL is entered in an attribute of type 'External source', it will no longer be emptied automatically. In addition, a functional message is given regarding the incorrect input.

  • PIM-4547: In the selection of circular relationships (eg related items / upsell / cross sell) a performance improvement has been applied.

  • PIM-4502: If an incorrect VAT number was entered, this caused an error.lazy.component error message when accessing the history of this record. This has been adjusted so that it is handled correctly.

  • PIM-4501: If an incoming relation was opened via a record (an example is that a contact is opened, and from there the compony),
    this caused the error message "The screen had to close: The node has been removed" when editing. This has been adjusted so that editing relations is now possible.\

  • PIM-4499: The filtering in the 1-n relationship screen did not work properly. This has been adjusted.

  • PIM-4493: The correct records are always displayed in the 1-n relation screen. Also clicking on the 'Refresh' icon works correctly.

  • PIM-4479: In the workflow module, scheduled tasks tab, it is now possible to filter by date.

  • PIM-4476: Adding an export workflow through the workflow history is again normal in terms of performance.
    In addition, a small performance improvement has also been implemented in the approach to the 'Jobs scheduled' tab in the workflow module.

  • PIM-4465: In some cases, logging in via delegation gave a fatal error message. This was caused by an Excel export being started at the same time. This has been fixed in this version.

  • PIM-4453: If the domain name contains a -, this meant that you could not adjust the starting number of an attribute of the automatically increasing type in the blueprint. This has now been corrected.

  • PIM-4449: When adding relations via the bulk change wizard, account is now also taken of the granted rights that someone has.

  • PIM-4442: An improvement has been applied to the login API when logging in.

  • PIM-4370: Een verbetering is doorgevoerd in de stabiliteit van de create API.

  • PIM-3448: The history of entities has been adjusted. For example, the import caused mutations in history, while fields were not changed. Now only changed mutations are displayed. Also when changing / adding relationship attributes, this is now correctly displayed in the history of an entity.

  • PIM-4499: The filtering in the 1-n relationship screen did not work properly. This has been adjusted.

  • PIM-3441: If a Boolean attribute was emptied by an import, this was not correctly presented in the history of an entity. This has been adjusted.

  • PIM-4361: In release 1.8.3.4 an adjustment has been made that makes it possible to filter on BLOB, BLOB collection and Thumbnail attributes.
    Via this issue, a re-indexing has been applied to all entities, so that filtering for these attribute types is also possible for all records already present.

JIRA issues (internal use)

key summary type created updated due assignee reporter priority status fixversions
Loading...
Refresh