GDT Where Used Tool v1.0.0.20

Ryden

I've found a problem with an array of a table not being detected in 10.0.0.19.

Se Table 49, the only function that appears to be used is CalcVATAmount.
However check in CU90 for multiple examples.

InvPostingBuffer[1].SetAccount(
        GenPostingSetup."Purch. Line Disc. Account",
        TotalVAT,
        TotalVATACY,
        TotalAmount,
        TotalAmountACY);

Nor does this line turn up for T49.Type

InvPostingBuffer[1].Type := InvPostingBuffer[1].Type::"G/L Account";

Edit:
Also Codeunit 5986 uses SetAmounts(), this is not shown either

Ryckutis

HI, GDT team. Not sure if you still support GDT Where used version or not (I have version 1.0.0.20) . but worth trying.
If there is a code like BomComponent[Level].Quantity
field Quantity is not shown as used in this instance. Probably due to record used as array.
Regardas,
Ricardas.

Ryckutis

Hi, GDT team. After Windows 10 update (it is Version 1709 (OS Build 16299.125) application could not be run anymore. Application can not be started.

Event viewer has logged .NET Error:

Application: GDTWhereUsed.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Xml.XmlException
at System.Xml.XmlExceptionHelper.ThrowXmlException(System.Xml.XmlDictionaryReader, System.String, System.String, System.String, System.String)
at System.Xml.XmlUTF8TextReader.Read()
at System.Xml.XmlBaseReader.IsStartElement()
at System.Xml.XmlBaseReader.IsStartElement(System.Xml.XmlDictionaryString, System.Xml.XmlDictionaryString)
at System.Runtime.Serialization.XmlObjectSerializer.IsRootElement(System.Runtime.Serialization.XmlReaderDelegator, System.Runtime.Serialization.DataContract, System.Xml.XmlDictionaryString, System.Xml.XmlDictionaryString)
at System.Runtime.Serialization.DataContractSerializer.InternalIsStartObject(System.Runtime.Serialization.XmlReaderDelegator)
at System.Runtime.Serialization.DataContractSerializer.InternalReadObject(System.Runtime.Serialization.XmlReaderDelegator, Boolean, System.Runtime.Serialization.DataContractResolver)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(System.Runtime.Serialization.XmlReaderDelegator, Boolean, System.Runtime.Serialization.DataContractResolver)

Exception Info: System.Runtime.Serialization.SerializationException
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(System.Runtime.Serialization.XmlReaderDelegator, Boolean, System.Runtime.Serialization.DataContractResolver)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObject(System.Xml.XmlDictionaryReader)
at A.C.A()
at A.D..ctor()
at A.f.A()


Event viewer has logged Application Error:

Faulting application name: GDTWhereUsed.exe, version: 1.0.0.20, time stamp: 0x587f7ddb
Faulting module name: KERNELBASE.dll, version: 10.0.16299.15, time stamp: 0x4736733c
Exception code: 0xe0434352
Fault offset: 0x0000000000013fb8
Faulting process id: 0x387c
Faulting application start time: 0x01d3797833fc2704
Faulting application path: C:\Users\Ricardas\AppData\Local\Programs\GDT Where Used\GDTWhereUsed.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 48cd5393-f0ef-4409-8ce3-97dd3d7b45d2
Faulting package full name:
Faulting package-relative application ID:

Ryckutis

Ryckutis wrote: »

Hi, GDT team. After Windows 10 update (it is Version 1709 (OS Build 16299.125) application could not be run anymore. Application can not be started.

Event viewer has logged .NET Error:

Application: GDTWhereUsed.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Xml.XmlException
at System.Xml.XmlExceptionHelper.ThrowXmlException(System.Xml.XmlDictionaryReader, System.String, System.String, System.String, System.String)
at System.Xml.XmlUTF8TextReader.Read()
at System.Xml.XmlBaseReader.IsStartElement()
at System.Xml.XmlBaseReader.IsStartElement(System.Xml.XmlDictionaryString, System.Xml.XmlDictionaryString)
at System.Runtime.Serialization.XmlObjectSerializer.IsRootElement(System.Runtime.Serialization.XmlReaderDelegator, System.Runtime.Serialization.DataContract, System.Xml.XmlDictionaryString, System.Xml.XmlDictionaryString)
at System.Runtime.Serialization.DataContractSerializer.InternalIsStartObject(System.Runtime.Serialization.XmlReaderDelegator)
at System.Runtime.Serialization.DataContractSerializer.InternalReadObject(System.Runtime.Serialization.XmlReaderDelegator, Boolean, System.Runtime.Serialization.DataContractResolver)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(System.Runtime.Serialization.XmlReaderDelegator, Boolean, System.Runtime.Serialization.DataContractResolver)

Exception Info: System.Runtime.Serialization.SerializationException
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(System.Runtime.Serialization.XmlReaderDelegator, Boolean, System.Runtime.Serialization.DataContractResolver)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObject(System.Xml.XmlDictionaryReader)
at A.C.A()
at A.D..ctor()
at A.f.A()


Event viewer has logged Application Error:

Faulting application name: GDTWhereUsed.exe, version: 1.0.0.20, time stamp: 0x587f7ddb
Faulting module name: KERNELBASE.dll, version: 10.0.16299.15, time stamp: 0x4736733c
Exception code: 0xe0434352
Fault offset: 0x0000000000013fb8
Faulting process id: 0x387c
Faulting application start time: 0x01d3797833fc2704
Faulting application path: C:\Users\Ricardas\AppData\Local\Programs\GDT Where Used\GDTWhereUsed.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 48cd5393-f0ef-4409-8ce3-97dd3d7b45d2
Faulting package full name:
Faulting package-relative application ID:

Actually it is nothing to do with Windows update. There was something wrong with files, which GDT generates behind the scene. It keeps files in
C:\Users\"name"\Documents\GDT IT Consult
And even if you uninstall GDT then install again these files are there.. which causes issues. I just deleted those files and GDT launched.
Ricardas.

primeap

unfortunately this does not work with NAV 2018..

tom66tom

Dear forum members,

the version GDT Where used will not be supported anymore.
You can continue to use it as you like.
For our Pro Version GDT Where Used PLUS we offer
on the other hand support and updates for current Dynamics NAV versions.
Your GDT Where Used Team