0
Category:
STATUS DETAILS

Comments

Please, let's get this feature, to finally close this decades-old gap, and save developers having to copy-and-paste ToolTips to every page/extension, which are guaranteed to drift apart over time. Thanks!

Category:

Very important report for all countries

Category:

????

Category:

This is essential. Moving Serial number by serial number is highly inefficient.

Category:

Absolutely essential requirement in order to be able to feasibly use these fields. I have worked with manufacturing companies with the number of released products in the hundreds, potentially even thousands. Any form of manual data entry for fields would be a huge effort.

Category:

Excellent idea. It is often a requirement to maintain multiple shipping locations and it is difficult currently to populate these locations on warehouse work without considerable manual intervention.

Category:

Hello,

we could also use this well,
can you give us an update?

Category:

In my opinion, it is not so much about wanting the configured products to be going through a extensive 'creation, reviewing, releasing and accepting' flow like you would do for a regular 'Engineered' product: you want to 'configure' a product via a model and be able to sell it right-away. The configuration model is supposed to guarantee the validity of the result so it can be used on a transaction immediately. The point of supporting 'Engineering' is that the starting point of such a configured product (a variant) may be a product that IS engineered and may be based off of a certain Version even (determined perhaps by the configurator model version you used to configure a new variant) and to be able to track that relationship. I would need to better understand the forthcoming support for variant creation in 10.0.21/22 to get this clearer but it is certainly a scenario that needs to be supported in some way (rather than having to setup a separate, non-engineered product in parallel to be able to configure)

Category:

As far as I can see, the Event Registrations entity still does not show in the list of Base record fields, on a duplicate detection rule...This has NOT been resolved.

Category:

Is this feature not available yet? even in 2021 release Wave 2? We are being forced to key in lat & long but as mentioned above by Boris, NO address fields given in Org Unit form, and button to GeoCode. Pls incorporate this feature asap since you are forcing us to provide lat&long in while we create Bookable Resource of type Equipment/Facility

Category: