>

System fields on Event level are not populated

Laura de Jong

Hi team,

My customer is trying to create some views and reports and it happens that 6 fields on Event Level are not populated where you would expect numbers coming out. 

Ordered Margin Field Key: 385145

Ordered Cost Field Key: 370076

Ordered Revenue Field Key: 370070

Actual Margin Field Key: 385147

Actual Revenue Field Key: 370071

Actual Cost Field Key: 370077

One Event is done so you would expect actuals values the other Event is in planning so you would expect ordered values:

 

The customer is now using a workaround with summary and formula fields. Is there something we missed in the set up? How should these field be used?

This is for CCIB Barcelona and they've submitted a ticket but addressed it with me in a meeting as well.

Anthony Costantino ?

Seth Halvaksz adding you as we have a related issue with Jaarbeurs and the Performance Project where we want to reduce the amount of summary fields and if we can use these standard fields that would really help.

Minka Verkaar as you work with these customers on SD.

 

Comments

8 comments

Date Votes
  • Official comment
    Anthony Costantino

    Laura de Jong - When you load those fields on the Edit Event page layout, you'll see that the Revenue and Cost fields are INPUTS. They do not autocalculate. The margin field auto-calculates the difference between the correspondiing revenue and cost values entered.

    These are legacy fields. The best practice IS to use summary custom fields as client has found.

  • Seth Halvaksz

    Laura, sounds like a bug. If so, it should go through support.

    What is the case number?

  • Laura de Jong

    This is the Zendesk ticket: https://ungerboeck.zendesk.com/agent/tickets/389118 , I see there is no JIRA case yet. I'll ask Support to create and post it here.

  • Seth Halvaksz

    If it is confirmed as a bug, it should be addressed in the jira ticket. We only use documentus to confirm if its a bug or working as designed.

    Or is your question if there's a workaround? I'm not sure i understand this:

    “The customer is now using a workaround with summary and formula fields. Is there something we missed in the set up? How should these field be used?”

  • Joppe Borsboom

    Thank you for the Documentus post, Laura de Jong! 
    Seth Halvaksz, we have created Jira ME-8557

  • Laura de Jong

    Seth Halvaksz  I wanted firstly to check if it is a bug. If not a bug, then we would like to know how it can work.

    Joppe Borsboom  thank you for your quick actions! 

  • Seth Halvaksz

    I looked at the steps-tor-reproduce for the ticket (ME-8557) and it just points to the customers database.

    Joppe Borsboom Can this be reproduced in QE?

  • Seth Halvaksz

    Joppe Borsboom 

    I saw your comment in ME-8557 that you can reproduce in QE.

    Is there a support article that references how these fields are populated? Could you post here please.

Please sign in to leave a comment.

Didn't find what you were looking for?

New post