Skip to main content

Error: Error executing code: Wrong argument types for comparison. (C)\Classes\xRecord\toolTipField (C)\Classes\FormDataObject\toolTip (C)\Classes\FormStringControl\ToolTip

Error: Error executing code: Wrong argument types for comparison. (C)\Classes\xRecord\toolTipField (C)\Classes\FormDataObject\toolTip (C)\Classes\FormStringControl\ToolTip







I faced a issue when I select a record on form,


 


Error executing code: Wrong argument types for comparison.



(C)\Classes\xRecord\toolTipField
(C)\Classes\FormDataObject\toolTip
(C)\Classes\FormStringControl\ToolTip


 


 


 


Solution:


Just check your EDT which is your primary key of table. check the relation.








Basically this error will come when you change the field name in table it will not update in your EDT relation.









































Comments











Post a Comment




















Popular posts from this blog



















Process of Sales order in Technical terms in D365Fo




























 ðŸ”¥ Sales Order Technical Flow in D365FO  (Creation → Confirmation → Picking → Packing Slip → Invoice → Accounting)   1. Sales Order Creation  Tables    SalesTable  → SO header    SalesLine  → SO lines    CustTable  → Customer master    InventDim / InventDimCombination  → Dimensions    InventTable / EcoResProduct  → Item master    Framework Classes    SalesTableType / SalesLineType    Responsible for validation, defaulting, creation logic      Key Methods    SalesTable.initValue()    SalesLine.initFromSalesTable()    SalesTable.validateWrite()    SalesLine.validateWrite()    Events (Extensions)    SalesTableType.createSalesTable()    SalesLineType.createSalesLine()     2. Reservation (Optional)  If reservation is done:  Tables    InventTrans  (Reservation status)    InventReservation    Classes    InventUpd_Reservation    InventTransReservation    Reservations impact picking and inventory availability.   3. Sales Order Confirmation  Confirms order and freezes price/quantity.  Posti...




















Post a Comment









Read more




























Top 200 Q&A in D365FO Technical




























  SECTION 1 — X++ BASICS (10 Q&A)  1. What is X++?  A proprietary object-oriented language used in Dynamics 365 Finance & Operations for business logic, similar to C# but integrated with D365 runtime.  2. What is a TableBuffer?  It is an in-memory object referencing a table. Example: CustTable custTable;  3. What is difference between select  and select firstonly ?  select  → returns all matching rows  firstonly  → returns only the first matched row  4. What is ttsbegin  & ttscommit ?  Used to wrap database transactions; ensures atomicity.  5. Can we write SQL queries directly in X++?  No. X++ uses a database-abstracted select  statement.  6. What is a container?  A collection datatype used to store mixed data types.  7. Difference between container and map?  Map stores key-value pairs; container is indexed and immutable.  8. What is a temp table?  A table that stores data temporarily in memory or database depending on property.  9. What is recursion in X++?  A method c...




















Post a Comment









Read more




























Process of Purchase order in Technical terms in D365Fo




























  Purchase Order Technical Flow in D365FO (Step-by-Step)  (From creation → approval workflow → posting → product receipt → invoice → accounting)   1. Purchase Order Creation  Tables involved    PurchTable  → PO header    PurchLine  → PO lines    VendTable  → Vendor master    InventDim  / InventDimCombination  → Item dimensions    EcoResProduct  / InventTable  → Item master    Classes / Framework    PurchTableType / PurchLineType    Framework that controls creation, validation, defaulting.      Key methods    PurchTable.initValue()    PurchLine.initFromPurchTable()    PurchTable.validateWrite()    PurchLine.validateWrite()    Events (Extension points)    PurchTableType.createPurchTable()    PurchLineType.createPurchLine()     2. Purchase Order Confirmation  Document Status update    PurchTable.DocumentState  → Confirmation    PurchParmBuffer tables  used for versioning.    Posting Class    PurchFormLetter_Confirm    Called internally via PurchFormLetter::construct(DocumentStatus::Co...




















Post a Comment









Read more