157
Can you allow for existing objects for Item Attribute 7500 to support different record types and not just items? If the table structure can work on generic Table Id concept it can be enhanced by partners to support other master records through subscribers and new page actions from extension.

We are currently using Item Attribute objects in our extension to allow adding attributes to other master records like: Fixed Assets, Employee, Customer, Vendor,..

We enhanced original objects to work with generic Table Id concept and not just Item record (TAB27). We found that many of the original functions in Item Attribute management already support that structure,

Adding attributes and filtering based on attribute value can work also when attributes are added on pages for Fixed Assets, Customers, Vendors...

The biggest downside currently for using existing Item Attribute objects is that Caption, labels, Text Constants are hard-coded with words like 'Item' and 'Item Attribute'. This would need to be refactored to use value from record like "Table Caption" so that for attributes assigned to Table Id 5200, Page Caption and all errors would use Employee Attributes,
Category: Inventory
STATUS DETAILS
Under Review
Ideas Administrator

Thank you for your feedback. We are adding it to our roadmap

Sincerely,
Andrei Panko
PM, Microsoft

Comments

I

I think its a great idea for all records, but particularly where an Item is configured to create a Service Items it would be really useful if the Service Items inherited the attributes and attribute values from the Item

Category: Inventory

I

I think specially this is very interesting for the item variants. If they could have attributes, the catalog will be much more flexible and searchable.

Also would be nice to have a matrix in order lines, where you could assort the Order Line Quantity. For example, say a shirt comes in 5 colors and 5 sizes, We would create 25 item variants with 2 attributes, size and color.

In stead of creating 25 order lines when we need this product, we would only create 1 line with the total quantity. Then in a modal page, we could assort this and specify the quantity for each variant.

Indeed this would be very usefull for a lot of industries like fashion, electronics, commodities,etc..

Category: Inventory

I

It would be great that the attributed can be attached to other master data records, such as customers. And when the selected attribute is visable as a column in the list page of the record.

Category: Inventory

I

It would be great if at least some Attributes would also easy filterable in Master Data Lists and Reports. In my opinion the solution are flowfields. It would be great if it is possible to mark a firm number of Attributes as filter Attributes and than create flowfields on item (master) table which Shows the value of the firm Attributes (including a CaptionClass the get the Name of the Attribute).

Category: Inventory

I

The idea is excellent and is used or copied by us. Since the programming is sometimes hard on the item and variant table, we have broken up this possibility and made it variable.
A very clear "thumbs up" for the idea. We are waiting for the implementation on the part of Microsoft.

Category: Inventory

I

What I personally would need is the possibility to attach Attributes to custom tables that consist of a composed primary key (e.g. Item No., Variant Code). In order to use the current Item Attribute table structure, I would need to add an internal Code20 field to my custom table and fill it with some unique ID.
Pity that the Item Attributes do not support being attached to GUIDs/SystemIds but Code20

Category: Inventory

I

Yes, this should exist for all major entities (Customer, Vendor, Fixed Asset, Resource, Employee). It would also be good to have Attributes against Item Variants. Variants are often used for things like colour versions of products and therefore will have different attributes from the 'parent' item.

Category: Inventory

I

I wish this was already here,
Dynamics GP has user defined fields, QB enterprise has custom fields that can be filtered for reports and those fields are available in report layouts for printable sales documents without having custom extensions made. D365BC has no customer attributes or custom fields and we need them. If we do ever get them, please make them available in the XML datasets on the custom report layouts so they can also be printed on our documents, not just visible on screen.
Currently we use home page field and the fax field as custom fields that our business needs. We use sales orders as work orders and need that information to be available to the field crew that gets the work order. currently "home page" is "gate code".

Category: Inventory

I

I think this is a great idea!
The design already allows for this, so it would be a question of renaming "Item Attributes" to "Record Attributes" or just plainly "Attributes".

Category: Inventory