0
Category:
STATUS DETAILS

Comments

Great idea!

Category:

I have given another vote for it. If a webshop has a filter function using price range need a certain price for an item per customer (in case of b2b scenario). It means somehow need to synchronize prices regularly.

Category:

+1

Category:

This problem is very frequent.

The solution should be based on proper methods for engineering change management.

Starting point 1: implement version management. Once a new release of a component leads to change in the FFF (form-fit-function) then it should obtain a new item number. That part may be an asset, or a subcomponent (part of the BOM). When it is not a maintainable item (ie not represented in the asset tree) then it should be represented as a sparepart.

Starting point 2. Change of subcomponents, should lead to a new version (with change date) on the next-higher level. That would be the BOM of the asset, and the asset itself.

The solution should then consist of 3 changes:
1. Versioning on BOM's. Version number (internal numbering) with change date.
2. Change of parts in the BOM, should automatically trigger version increase.
3. Versioning on Assets. Like BOM.

Category:

This could take the form of RecordRef.ModifyAll(FieldNo, OldValueVariant, NewValueVariant, RunTrigger)
and would act the same as Record.ModifyAll(Field, OldValue, NewValue, RunTrigger).
This seems like the most logical syntax and most consistent with how records and RecordRefs do things currently.

(I presume doing it as FieldRef.ModifyAll(OldValueVariant, NewValueVariant, RunTrigger) is undesirable and perhaps not possible, as then you're telling a reference to a field in one record to actually modify all in its parent RecordRef.)

Category:

The field "User Group Code" is useful in order to give an user the possibility to see from which User Group this page was called. User can also change the filters and jump to some other user group. Additionally the page can be used for other related Idea:
https://experience.dynamics.com/ideas/idea/?ideaid=2394052a-664c-ec11-a3ee-0003ff45af50

Category:

I believe the old behaviour was that the sorting drop-down would be offered for any DataItem in which the developer had not specified a DataItemTableView sort order in code. That makes sense since if they do specify one, there's probably a reason, and if a user could override the developer's sort order it might break such reports.
(The other way is to do it with SetCurrentKey() in OnPreDataItem(), and that'd still show the sorting drop-down, but then the code would override it...)

Category:

I have a requirement to do define main account for Un-, realized loss/gain by Customer/Vendor group.

Category:

It seems the ideas in the links below are discussing the same topic with this one.
https://experience.dynamics.com/ideas/idea/?ideaid=92373813-de4b-e911-867a-0003ff68f7ae
https://experience.dynamics.com/ideas/idea/?ideaid=1133f8c4-ddf9-e811-a140-0003ff68f5dd

There may be other ideas that is essentially same as this.
I think it is no good for everyone who needs an enhancement that it is scattered in several topics and gets less votes than the number of potential people who needs it, as a result.

Now that this is under review, I hope Microsoft does recognize those ideas that can be regarded as same idea and count the votes as real number of people who needs it and propel it further.

Category:

It seems the idea in the link below is discussing the same topic with this one.
https://experience.dynamics.com/ideas/idea/?ideaid=1133f8c4-ddf9-e811-a140-0003ff68f5dd

There may be other ideas that is essentially same as this.
I think it is no good for everyone who needs an enhancement that it is scattered in several topics and gets less votes than the number of potential people who needs it, as a result.

Now that this is under review, I hope Microsoft does recognize those ideas that can be regarded as same idea and count the votes as real number of people who needs it and propel it further.

Category: