0
Category:
STATUS DETAILS

Comments

A recommended functionality.

Category:

My colleagues and I are considering this to be a major loss in analysation options since we moved from Click Dimensions to Customer Insights - Journeys and would really appreciate this feature in CI - J.

Category:

As Portugal is a country and the original language of Portuguese this must be included

Category:

We are using a multiple Apps-Customer-Model. Often we need to move Objects from one App to another to keep reachability in more than one App. In our testenvironment we then get the problem not being able to install the new App with powershell, because the old App still contains the moved object.

We have to deinstall all Apps before we can install all the new apps in the test-Sandbox all together.

It would be very helpful to automate this process.

Category:

¡It is necessary to resolve this as soon as possible!


I think this is not a new idea. I think this is a bug (Bad design) in "Variant Code" and Manufacturing implementation.


¡Its resolution takes no more than 15 minutes!


The extension of manufacturing management to products with variants, should:

• add "Variant Code" in table "99000774 Family Line" 

• modify in codeunit "99000787 Create Prod. Order Lines" the CopyFromFamily procedure.


In this procedure should modify call to InitProdOrderLine adding the "Variant Code"


local procedure CopyFromFamily(): Boolean

var

Family: Record Family;

FamilyLine: Record "Family Line";

ErrorOccured: Boolean;

begin

Family.Get(ProdOrder."Source No.");

FamilyLine.SetCurrentKey("Low-Level Code");

FamilyLine.SetRange("Family No.", ProdOrder."Source No.");

OnCopyFromFamilyOnAfterFamilyLineSetFilters(FamilyLine, ProdOrder);

if FamilyLine.FindSet() then

repeat

if FamilyLine."Item No." <> '' then begin

//Original

// InitProdOrderLine(FamilyLine."Item No.", '', ProdOrder."Location Code");

//New

InitProdOrderLine(FamilyLine."Item No.", "Variant Code'', ProdOrder."Location Code");

//EndChange

OnCopyFromFamilyOnAfterInitProdOrderLine(ProdOrder, FamilyLine, ProdOrderLine);

ProdOrderLine.Description := FamilyLine.Description;

ProdOrderLine."Description 2" := FamilyLine."Description 2";


Category:

Dear Beatriz Nebot Gracia (administrator),

I do not understand:

you quoted “We're adding this idea to our long term roadmap and we expect it would be released in the coming waves”

but is also already confirmed as planned !!!!


Is planned or not ?

please involve Product Group !

Marco Squinzi


Category:

Must-have!

Category:

Now we are in march 2024.

The first time that this problem has been shared with Product Group is earlier 2019....

And it has been regularly solicited every 6 months.

Every time that a Company in the world export has to report HSCODE (or CommodityCode or HTS as you prefer) and Country of Origin to allow Custom to calcolate import duty.

Why you released x USA and CANADA, AUSTRALIA, (Not intrastat) and is not released for Puerto Rico or Argentina or any Asian Countries with Microsoft Localization ?

Will be the Foreign Trade available in the new Latin America Localization that Microsoft is releasing ? And in the other new localization ?

Is really Microsoft interested to release this functionality ?

Many company and partner are waiting this easy fix to get the delocalization of the foreign trade tab to every country and every localization.

Please share in which PU Microsoft will release the functionality, or provide the sysflight to activate it !

Else tell us that Microsoft will not do and every one will make its own customization to fixit... knowing that they will not go back to fixit when Microsoft will release this functionality.

Marco Squinzi

Category:

Please add to the roadmap. We more and more requests for this, certainly in situations where goods went out and come back (rental and inhouse repair).

Category:

Would be great to have this in standard functionality!

Category:

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 500