Apply deployable package via LCS using a mobile device


When you try to apply a deployable package to a non-production environment via LCS using a mobile device, picking the right deployable package is kind of Russian roulette. Currently on android phone and iPads the experience is, that you are only seeing the columns "Modified by" and Publisher, ...

Read more...
2 Comments

Read more...
2 Comments

Category: Lifecycle Services (200)

STATUS DETAILS
Under Review

Specify location id or location profile (of the put location) on work processing policies (for deferred put)


Within the work processing policies (for deferred put) it would be very helpful to specify the location id or the location profile (of the put location) to reduce the range of location where you want to use deferred put. This new setup could be used to setup different policies for put to bay door...

Read more...
0 Comments

Read more...
0 Comments

Category: Warehouse management (422)

STATUS DETAILS
Needs Votes

Track sign-off by and sign-off date time on deployable package


Via sign off of a deployable package in LCS, the deployable package gets marked as a release candidate. On a SOAX governed project we got the requirement to track/log this action via individual field. Currently modified by and modified data time is used to track this change, with the effect that ...

Read more...
0 Comments

Read more...
0 Comments

Category: Lifecycle Services (200)

STATUS DETAILS
New

Schedule multiple instances of index defragmentation/maintenance batch job


Currently it is possible to have one instances of index defragmentation/maintenance batch job. Additionally, the setup for “System job maximum execution time”, “Count of indexes”, “DTU threshold” and “Run in an offline mode” could only be done once per D365FO instance. We would want to schedule ...

Read more...
0 Comments

Read more...
0 Comments

Category: System administration (219)

STATUS DETAILS
New

Show which user has enabled a feature in feature managment


We recently had the problem that one user activated several features by mistake. To find the corresponding user we had to use the TableBrowser for table FeatureManagementMetadata, but it would be much better if we could see this directly in the feature management workspace.

Read more...
0 Comments

Read more...
0 Comments

Category: System administration (219)

STATUS DETAILS
New