-
Setting the user in-active automatically from Azure once they're removed/deleted from E-commerce B2B website
When a user is removed from the list of users who can access the business-to-business e-commerce website, the corresponding customer record is removed from the business partner's customer hierarchy record in Commerce headquarters.
However, the customer record itself isn't deleted from Commerce headquarters.
If the user's status hasn't been updated to reflect their removal, they might still be able to log in and place orders.
To prevent the user from logging in or placing orders in the E-commerce website, they need to be set to inactive or removed from the Azure portal.
So, what the customer is looking for is that they don't mind that the user record will not be deleted from HQ or not. They just want that once the user is removed/deleted from E-commerce website, it automatically set the user as Inactive in Azure to block the removed user from logging into the website or place orders.
They don't want to manually set it inactive.
-
Enhance Product Search Visibility Based on User Login Status and Customer Specific Catalogs
In the current Dynamics 365 Commerce system, all products assorted with the store are visible in the search results, irrespective of the user's login status. This feature request aims to provide more granular control over product visibility in search results based on the user's login status and their specific customer catalog.
Specifically, the feature should allow administrators to configure certain products to only appear in search results for specific logged-in customers. These products should be invisible in search results for users who are not logged in or do not have the specific customer catalog assigned to them. This feature would enhance the B2B shopping experience by ensuring that customers only see products relevant to them, and it would protect the visibility of customer-specific products from users who are not logged in.
This feature could potentially be implemented by extending the current product assortment functionality to include visibility rules based on user login status and customer catalog assignments. The system should check these rules when generating search results, ensuring that each product in the results is appropriate for the current user's context.
This feature would provide businesses with more control over their product visibility, enhancing the shopping experience for their B2B customers and protecting the exclusivity of customer-specific products.
-
Lock ability to zoom on commerce app.
Can you add an option/feature to restrict the ability to zoom in and out on a touch screen device within the Store Commerce app/POS.
Currently it tries to reshape the POS and causes issues with visibility. re-opening the POS resolves this but is not a desired resolution, especially when you're in a middle of a task such as store transaction or any other POS process.
-
Change DMF behavior to support bulk update for attributes / Best practice on where we can update the Variant based attributes.
Customer wants to use excel add in when he is looking for data entity to use to use DMF projects to import the data instead of the add in.
We checked the data entity the excel add-in uses RetailTmpBulkProductAttributeValueEntity and data management is set to no.
Can we change the behavior of this entity to be set to yes? Or add any other entity that supports DMF projects?
-
A way where "MediaServer" does not get deleted from IIS when you upgrade your environment.
When using a MediaServers created through IIS for all self-hosted environments.
After installing the latest version or any version update, we see that the MediaServer is deleted from the IIS during upgrade. Can you add a way or any workaround to avoid this situation?
The current workaround is to go to each CSU server and manually recreate it, but this is time consuming and isn't very efficient overall.
-
Support "Replace alternative item defaults on sales lines" with retail Ecommerce B2B websites
Customer is using "Replace alternative item defaults on sales lines" feature which is working fine for HQ.
However, they also want to implement such a feature to work with retail Ecommerce B2B website, not only SCM.
The scenario is that B2B customers buy spare parts or items through the website and due to huge number of parts available sometimes they're not available or there's a replacement.
If the order is through HQ and the feature is in use, it works fine and we can automatically replace the item if there's an alternative setup for it.
However, if the order is created from the B2B website, the CST doesn't get a notification or a prompt that this item isn't available, or if there's a replacement for it. This has to be done manually from HQ and due to that, sometimes the replacement they get is a complete different item, or a much more expensive item.
So, if we can implement that the same feature for Retail Ecommerce B2B websites that would be great as many business will rely on such feature especially for selling spare parts that has many alternatives.