Kurt Hatlevik DXC.technologies Vertical lead Retail(Login with hotmail personal account)

The performance of the sales order form is currently very slow. The main reason for this is that the form SalesTable currently have 35 data sources on the form itself. In addition 2 additional tables have been added on the form extensions. So just to open the form, close to 37 data sources are queried. This is madness and not maintainable from ALM or performance perspective. I therefore suggest that it should be considered to introduce some new simplified forms for Customers, Vendors, Sales order and Purchase orders. The new forms will live side-by-side with the larger forms, and are focused on simplified registration of SO's and PO's. The core concept is to have some very fast forms for registration and query.

The similar concept have already been done for "planned orders simplified", and the idea is to extend this vision of simplicity as an option. In essence the new Sales Table form should contain only relevant fields from SalesTable, SalesLine and inventDim.

Please evaluate as I'm tired of waiting 6 seconds for the sales order overview to open, and 5 seconds for the sales order details view to show up.

It would be great and interesting to try out suppressing null and default values when serializing ODATA/JSON payloads. It would be interesting to see if if can shave off payload and a few milliseconds in network connectivity.

Can you please try out the effect of this ? For situations with limited network bandwidth it could have a very positive effect :-)

Here is a small C# samplecode on how to reduce the JSON payload.

using System.Runtime.Serialization;
using System.Text.Json;
using System.Text.Json.Serialization;

[DataContract]
public class TestClass
{
    [DataMember]
    public bool B1 { get; set; }

    [DataMember]
    public bool B2 { get; set; }

    [DataMember]
    public string? S3 { get; set; }
}

class Program
{
    static void Main()
    {
        TestClass tc = new() {B1 = true};
        JsonSerializerOptions options = new JsonSerializerOptions();
        options.DefaultIgnoreCondition = JsonIgnoreCondition.WhenWritingDefault;
        var serialized = JsonSerializer.Serialize(tc, options);

        Console.WriteLine(serialized);
   }
}

Prints: {"B1":true}

In the prospects form (smmBusinessRelationsListPage) add the possibility to filter on the field "Status of B2B prospect", so that is is possible to create tiles/lists on B2B prospects that is "pending"

When looking through the menues in D365 I see that more modules are having submenues in level 2+, and this looks a bit strange

If you look in the menus where you have a submenu on level 3+ the hierarchal view disappears when expanding the menu. This makes it harder to see when a submenu starts and ends. Why not also use indents on sub menues ?