Perfion Windows Client - Version 5.4

ECommerce API: Attributes can now be output from Multi-value features

ECommerce API: Fields holding multiple values can now be output individually

In previous versions of Perfion, features holding multiple values where, in the ECommerce API when mapped to a Field, output using sub-elements named Value:

<Field name="MultiValueLocalizable" culture="en-US"> <Value>Value A</Value> <Value>Value B</Value> <Value>Value C</Value> </Field>

Except when the multi value only held one value, where it would be output as an attribute named value:

<Field name="MultiValueLocalizable" culture="en-US" value="My only value" />

Now you can use the method-parameter OutputMultiValueFieldsIndividually to output each value as a separate field. The parameter is supplied to fx. GetProducts like this:

<Execute method="GetProducts"> <Parameter id="Channel" value="Channel A" /> <Parameter id="OutputMultiValueFieldsIndividually" value='true' /> </Execute>

And the result is now output with a separate Field-element per value, regardless of how many values there are (except if there are no values, in which case nothing is output):

<Field name="MultiValueLocalizable" culture="en-US">Value A</Field> <Field name="MultiValueLocalizable" culture="en-US">Value B</Field> <Field name="MultiValueLocalizable" culture="en-US">Value C</Field>

A new checkbox has been added to the grid language menu for enabling show of localized selectable values in same way as for explicit localized values.

A new checkbox has also been added to the Item Editor for enabling show of localized selectable values for other languages than current user language.

Optimized updating of data through PTable. The most significant performance increase will be seen when updating or inserting multiple values in the same Query.

The performance of the Supplier Import will be increased similarly, since it relies on the PTable to update database.

When a user changed own languages in 'Users and Groups' admin the users language list was not updated so e.g. Item Editor did not reflect the updated language list.

The update of the users own languages list requires a restart of Perfion, so a mandatory restart of Perfion is now enforced.

Before this version of Perfion, the only way to fetch data for a Swap-relation-feature was to do the following:

<feature id='MySrd' type='Relation' />

This would fetch data for the Swap Relation Table (SRD in the following).

You could include a view, and that would be used for fetching that specific relation:

<Feature id='MySrd' type='Relation' view='Family' />

Without a view only the base value for the MySrd-feature is fetched.

Now two select-options have been added:

Option 1: IncludeConfiguredSwapRelations

<Query>
  <Select languages='EN' options='IncludeConfiguredSwapRelations' >
    <Feature id='*' view='Item'/>
  </Select>
  <From id='ProductDefaultValues' />
  ...
</Query>

This will make Perfion fetch SRD for all SRD-features in the Item-view for the configuration of the Product-feature. Note that this can be combined with the explicit select of individual SRD-features. Using the option to fetch SRD will always make Perfion use the Config-view when fetching SRD-features.

Option 2: OnlyShowSwapRelationMarkers

Adding this option will make the Perfion API fetch the same SRDs as it otherwise would (explicitly selected or selected from configuration using the option), but instead of outputting the data, it will only output a marker that indicates that the feature holds data for the specific item.

Example: Instead of outputting the data as shown here:

<Product ...>
  <MySrd type="table">
    <MySrd id="123" parentId="0" ...>
      <Value seq="0">SRD1</Value>
    </MySrd>
    <MySrd id="234" parentId="0" ...>
      <Value seq="0">SRD2</Value>
    </MySrd>
  </MySrd>
  ...
</Product>

this will be output instead:

<Product ...>
  <MySrd type="table" data="1" />
  ...
</Product>

If some item (here Product) does not hold any data on the SRD-feature, nothing will be output for it for that product. This is just as is the case for all other features in Perfion.

When defining a new filter using the Filter dialog the filter handling would breakdown if id clause was specified using '_FeatureValidation' or '_FilteredValues' - e.g. using the WHERE clause '<Clause id='*._FeatureValidation' operator='ISINVALID'/>'.

This has been fixed.