Lookup Flowfield in SQL Server version

brauz
brauz Member Posts: 14
Hi guys,

I've been searching some information about Lookup Flowfields in SQL Server version but still having some doubts about the performance. I been understand that Sum Flowfields need to maintain key index, and if you create many of then you'll get a slower system. As I know, Lookup Flowfields not need to maintain any key, not are stored in DB and only gets the value when you show the field in a form or call the Calcfields Function.

Anybody have some expierence about create many lookup flowfields and if it make Navision work slow.

Comments

  • Marije_Brummel
    Marije_Brummel Member, Moderators Design Patterns Posts: 4,262
    A lookup flowfield will create a select statement on the lookup record with the parameters as filter.

    This can be slow if the parameters are complex, but usualy is fast.
  • brauz
    brauz Member Posts: 14
    I talked about the performance in general, not about the speed calculation of the field. For example, if I create some Lookup Flowfields in the General Ledger Entry table, this will make slower the Posting process who create many entries?
  • Marije_Brummel
    Marije_Brummel Member, Moderators Design Patterns Posts: 4,262
    During an insert of an entry the flowfields are generaly not calculated so it should not affect posting performance.

    Performance in general is a very complex subject and can be discussed for hours and hours and is different for every single installation.
  • kine
    kine Member Posts: 12,562
    It depends on settings of keys and SIFT. It means, if the flowfield is using some existing key, there is no problem. If you will need to create new key or SIFT, performance will change...
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.