-
Multiple product attributes to allow more advanced filters in webshop(s)
SANA (Add-on) supports filtering of products on a product list page, based on product attributes. For each product attribute, one or more attribute values can be specified in order to filter the results on the product page (based on attribute type and configuration). AX2012 does not support specification of multiple product attribute values for a specific product. This prohibits the following scenario. SAP does support this scenario and thus the SANA shop can show in which machines certain parts are used.
Imagine you have 10 machines. You also sell spare parts for these machines. Ideally, you'd want to specify for each spare part to which machines (note plurality) this product applies, so when opening the spare parts list page on the webshop, you can filter (check checkbox(es)) the machine(s) you're interested in buying spare parts for.
However, by default, you can only specify one applicable machine as a product attribute value (assuming you enforce referential integrity through using a product attribute type that uses fixed values).
To overcome this issue for now - although not ideally - we had thought of the following work around.
For each spare part product (i.e. all products in the spare part procurement category hierarchy), introduce product attributes 'Is applicable to <machine A>?' with a value either true or false. This would allow us to create product list pages in SANA Admin for each of the 10 machines, which would only display spare parts/products with their respective product attribute value set to true.
- Is there any way to accommodate this scenario using filters in SANA backoffice, instead of filtered product list pages? We would like to show a single filter criterion (i.e. 'Applicable machine', instead of 'Applicable to machine A?' true/false, 'Applicable to Machine N' true/false etc.) -
Auto disable user accounts how are disabled or removed in the (Azure) Active Directory
Hi,
I found this post and I am wondering if such a feature could not be default in D365FO?
https://community.dynamics.com/ax/f/33/t/200156
J. -
As a warehouse user I want to see in what environment and warehouse I am on the mobile device to avoid that I by incident ruin the warehouse inventory
We are testing for upgrade to Version 10. We have latest mobile warehouse app 1.6.1.0 with option to select 2 connection string. We added a connection to sandbox and production. That is nice, But the user cannot see if PROD or ACC (sandbox) is selected. In the browser version we had manually added a css-style sheet to change colors and put TEST in CAPS on the screen. Can the product team do the same for the APP so that users cannot by mistake run a day through the Sandbox or Production and thereby ruin the inventory....??? -
Refactor the warehouse app so that the code is better readable, (unit) testable and extendable
The productivity of our workers will highly increase if there would be less errors and flaws in the usability of the warehouse app. We cannot extend or work around it as it are about 3-6K codes/lines in one class/ function. -
119112921000456 As a warehouse inbound receiver I want a proper guided flow to receive RMA's on the mobile device
Try to execute a product recall for 300 items with serial numbers and with revisions and see that a worker is not able to execute. Errors all over the place in software bugs and workers not able to follow a consistent process. In the end end we fall back to the old school inventory picking with packing slip posting as every returned item.... It really does not make sense. To be honest: it is getting annoying as we do not see any improvement over the last 3 years. See support item: 119112921000456 and a photo of how our people need to work... -
Stop adding new functionality, first make what you have perfectly working
We see reoccurring issues and keep on reporting them. It looks like the focus is more on new ideas then on having a nice working system. It seems that new ideas are promoted but in general a solid working foundation to warehouse operations is not provided to our workers. -
Reward system to get paid for bug reports and product improvements
Many Microsoft Partners do not report bugs/ issues as they do not get paid for them. In this lucrative market with ICT shortage that is understandable. You can better have consultants paid on new functionality with quick fixes then to provide feedback on the product and follow up a proper implementation by Microsoft. By providing a paid rewarding system to customers and/or Microsoft partners are stimulated to provide feedback instead that the customer is bleeding/ spending money on it. -
Warn/ inform the user that no demand is created because of wrong BOM/ Route
Our factory was nearly out of stock because production orders had been created with a BOM not having all cost prices calculated. The order was not reflecting demand for underlying parts of the BOM. For scheduled orders it looked like although we are not sure as we fixed the cost price issue. A route detail was not setup properly and no cost prices had been calculated. it was hard to discover where the problem exactly was: Please improve: - warn user that data is incorrect and might lead to wrong planning data; provide a warning that there are production orders not working together with MRP; unclear if created production order or missing cost was issue..or missing group on route detail; - provide more information on errors generated during cost price calculation (cost category operation no 140 missing is not very helpful as operation no 140 cannot be found in a BOM with phantoms and multi levels); - improve the product information --> released products field as it says no cost price, but it parts do have a cost price per site. We have 2 sites setup. -
Use the actual DestinationPostalAddress to retrieve the container packing list to avoid 'There is no data available'
We got the error: 'There is no data available' because the user changed the customer address during picking by the warehouse. The issue has been reported here: "Issue KB 288520 Container Content report error when modifying customer address". V10.0.3 My idea is to retrieve the address as it was on that day of the shipment and before somebody changed it? Just paste the 'DestinationPostalAddress' to the address retrieval or am I missing something here? Thinking further if you want to clean up/ archive addresses. What address is then on the shipments/ and loads This will avoid that in the future somebody wants to print the container list...and the same issue re-appears. Issue 288520Container Content report error when modifying customer address Product and version: Finance and Operations Release: 10.0.3 RESOLUTION By design PROBLEM After changing the details of the customer address, the Container Content report is not working anymore. Error message: No Data available on report. REMARKS The actual result is a consequence of a design constraint when implementing data validity for addresses, including logistical addresses. The current design is such that WHSShipmentTable.DeliveryPostalAddress is added when the SO has been released to warehouse. Once the customer address is updated on the customer record, this update does not cascade update to active source documents such as sales orders as an example. The address originally applied as the WHSShipmentTable.DeliveryPostalAddress will as a consequence of this not be updated, similar to any sales order address, as the delivery address has expired - is no longer active. When such a situation occurs, then do the following: In the container contents Reports form select one container and click on Print containers contents. In the print dialogue, click on Filter under Records to Include. On the query WHSContainerContents form, Click on tab Date Options. Click the radio button Show Records Active As Of. Select a date in the past from before the address expired. This will print the Container Contents Report with the address originally applied for the Shipment. No hotfix will be released changing the current behaviour.
You’re offline. This is a read only version of the page.
