Skip to main content
Solved

Main reason to have naming differences in referring same data

T
Do Gooder (Employee)
Forum|alt.badge.img+4

What would consider as the main reason to have naming differences in referring same data in different part of the application?

For example, information shows in ‘Customer Invoice Types’ window under ‘Layout ID’ Column is as follows,

Same Information shows in "Report definition" window with a different naming, which is "Report ID"

What would be the main reason for such naming differences to exist in the application?

Is that due to the fact that development had handled by different teams at different time frames during the product life cycle?

Best answer by ShawnBerk

Not as a customer….never been told anything by a partner or employee.  I imagine it is different teams, different times, and no adherence to a standard with no quality control to ensure uniformity.  No different than Microsoft developing Office.  But that is all a skeptical theory, maybe your old time colleagues can say a better reason.

View original
    Did this topic help you find an answer to your question?
    This topic has been closed for comments

    3 replies

    S
    Superhero (Customer)
    Forum|alt.badge.img+28
    • ShawnBerk
    • Superhero (Customer)
    • 1482 replies
    • July 1, 2021

    Good question - there are these inconsistencies throughout IFS.  Find Supplier_Id in one place, supplier_no in another place, site is a view, site is a field, but table name is contract.

     

    It’s everywhere in IFS…..

    T
    M
    Sandaru Jayawardena
    3 people like this
    • T
      Tharindu Seneviratne
    • M
      Malisha Udugama
    • Sandaru Jayawardena
      Sandaru Jayawardena
    T
    Do Gooder (Employee)
    Forum|alt.badge.img+4

    Any specific reason observed for that?

    S
    Superhero (Customer)
    Forum|alt.badge.img+28
    • ShawnBerk
    • Superhero (Customer)
    • 1482 replies
    • Answer
    • July 1, 2021

    Not as a customer….never been told anything by a partner or employee.  I imagine it is different teams, different times, and no adherence to a standard with no quality control to ensure uniformity.  No different than Microsoft developing Office.  But that is all a skeptical theory, maybe your old time colleagues can say a better reason.

    Terms & ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings