Export product from a set of locales - locale

is there an option for the akeneo cartridge to export only the products from a given locale? Currently we export all the products on all the locales, which is not ok.
I want to use a localizable boolean attribute which controls whether the product is to be exported to a given locale in SFCC or not.
Should I touch the akeneo cartridge or is there already a functionality implemented for that?

Related

Can we export all Dialogflow entities at the same time instead of 1 by 1?

I have a lot of entities and i would like to export them all. I know i can click the export button next to each entity but that is annoying if i have to do this for each and every one.
Is there a way to export them all at the same time ?
I have tried to export the whole agent, but the entities do no get exported with it (they are mentioned in the Intents file but not in a file on their own)
If you export the entire agent, there will be a folder called entities which contain the information for all your Entities. Each Entity Type will have at least two files - one containing general metadata about the Entity Type, and the other containing the langauge-specific entries.

Liferay 7 Eclipse IDE override default categories filters query

I’m looking for a way to override the default category filter behaviour for Asset Publisher widgets (point 3 of my previous question here).
As far as I understand in the Setup > Asset Section > Filter a rule based on categories will look for all source > asset type components which match the selected categories.
I would like to know where is default query stored and how it is possible to modify it in order to introduce other custom criteria.
Update:
I can create a Liferay module project fragment, but I wasn't able to retrieve the correct OSGi bundle and relative file to override the default query filter behaviour.

How to set default value of ProductType attribute in Commercetools platform?

I wanna to set up default value if a ProductType attribute is empty or null.
This is the documentation I referred: https://commercetools.github.io/commercetools-jvm-sdk/apidocs/io/sphere/sdk/meta/ProductAttributeDocumentation.html
There is currently no default value that can be defined in product type attributes.
You could create a custom object for that purpose.
How do you plan to manage your product data?
Will you sync from an external system?

How to change the display field to use when use jdl?

When use jhipster entity generator by console a question like follow allows to change the display field on frontend:
When you display this relationship with AngularJS, which field from
'user' do you want to use? (id)
It is possible to make the same with jdl?
Edited
Ok, It appears that nobody has this problem, or maybe there aren't anybody in home?
So, I'm going to explain it. Let's suppose this scenario:
Create two (or more) entities with relationship with the console.
Choose a different field from id to manage the front-end.
Test the project (it works fine).
Export the model to jdl file
Import the jdl file, with no changes, in another new project.
Boom! The UI comes back to Id reference.
Is there any option to resolve it, or is this resolve in other tools like uml import? Future plans?
Resolved
Reading the documentation in detail, I've found a solution:
"Declare the field you want to use to display a relationship in AngularJS.
To do that you must add the field name between () after the injected field name."
Resolved
Reading the documentation in detail, I've found a solution:
"Declare the field you want to use to display a relationship in
AngularJS.
To do that you must add the field name between () after the injected
field name."

pimcore: updating objects with localized fields

I have a weird problem when updating objects in pimcore.
I've created a class containing some normal and also localized fields and then some objects from that class.
It is possible to edit all objects directly via pimcore, but the only ones which can be updated through controllers are the ones where all localized fields are filled, although some of these fields may not be used in the form. That is, an object won't be updated unless all its localized fields are filled before.
Any hints?
EDITED:
Here is a piece of code from my controller :
$newTitle = Object_TitleArchive::getById(251);
$newTitle->setName('New Name');
$newTitle->save();
It does not work unless all localized fields of the object are filled before or given now.
Revision: 3086
Check under Settings -> Object -> Classes, and then under the class you have defined. If the components placed under the localized field has the checkbox Mandatory Field checked, remove that check or fill in values for all required languages.

Resources