x Want to participate? Join the group to interact
  • State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 138 subscribers
  • Views 440 views
  • Users 0 members are here
Browse Forums
Announcements
237
topics
29
replies
General Discussion
5k
topics
13k
replies
Sage Data & Analytics
56
topics
95
replies
Sage Enterprise Intelligence
211
topics
418
replies
Sage Intelligence Reporting
121
topics
322
replies
chunheng

TRT folder. Significance of W* files

SUGGESTED
Posted By

Hi,

Would like to know the significance of the W* prefix files in TRT folder of each Sage X3 folders.

[1] Is it safe to delete W* prefix files in TRT folder on folders that is not named X3?

[2] What are the W* prefix files in TRT folder?

[3] How do I identify the non-W* equivalent from the TRT folder? For example, WGWOSDHALL = WGW+Windows+EntryTransaction = Sales Delivery, ALL entry transactions so I need to look at Sales Delivery's Entry transaction and fix the tables there before running entry transaction validation.

There was a customization issue which keep reoccurring upon validation so would like to know a way to link back to actual from W* prefix files.

  • 0
    SUGGESTED

    Hi,

    [1] No. Do not delete theses files

    [2] They are scripts generated when you hit the "Validate" button in several functions.

    [3] :

    • W0XXX à W9XXX : Screen XXX (0 = import, 1 to 9 = screen)
    • WATXXX : Purchase price XXX
    • WBTXXX : Sale price XXX
    • WFXXX : Query XXX
    • WGXXX : Window XXX
    • WJXXX : Web Service subprog XXX
    • WKXXX : Web Service object XXX
    • WM[A-J]XXX : Classes, context and representations XXX
    • WMKXXX : Workflow Rule XXX
    • WOXXX : Object XXX
    • WWCNSXXX : Consultation XXX
    • WWE431 : Export number 431
    • WWI134 : Import number 134
    • WWINIGXXX : Global variable initialisation GXXX

    These are the main ones but there are others.

  • 0 in reply to L.V. Expertise X3

    Hi 

    May I know if there is a official list I can refer to for [3] or can only be identified through manual labour of bookeeping and cross-checking with Sage X3 proper?

  • 0 in reply to chunheng

    The simplest way to find the real window or screen in the corresponding development functions paste the value into the left list. For screens, make note of the screen abbreviation and then filter by that abbreviation. The screen that doesn't start with a W is the original. Similarly for windows, search by the object assigned to it. The window code not starting with a W is the correct window. You can always find the window of a function by typing GBOITE into the calculator.

*Community Hub is the new name for Sage City