>

Confirm target field for SASIE code – API upload (Event data)

Francesco Torchia
  • Account name: Olympia Limited
  • Region: EMEA
  • Client version (Enterprise): 25.4
  • Description of the issue:
    The customer has recently enabled Open API write access on their Enterprise environment and is preparing an API-based upload of historical event data.
    They can already map and update the following Event fields via API:
    - Previous Event Number
    - Attendance Actual
    - Attendance
    However, they also need to upload a SASIE code from Excel and require confirmation of the correct target field in Momentus.
    They would like us to confirm:
    - Which Event field should be used for storing the SASIE code?
    - Whether this should be a standard Event field, Event Category/Sub‑Category field, or a custom Event UDF
    - The API field name (entity + property) for write access.
  • What you've already tried or suggested. Why does this not work?
    I searched for info about the SASIE code, that seems to refers to the Size and Scale Index for Exhibitions, a UK industry report. But I haven't found anything in our Knowledge base.
  • Business impact if not resolved: Delays in their planning
  • Attach relevant files (such as screenshots)
  • Links to articles where you've looked for solutions and also other steps you've taken to research the issue: N/A

    Pieter Fourie Mike Schepker Nicole Loh Satya Ram Nukala Any idea?

Comments

3 comments

Date Votes
  • Francesco Torchia

    Additional info from the customer:
     

    We want to know the feasibility or best option to complete the following.

    We have an excel file which has over 600 events, both historical and future.

    We would like to UPDATE Event Category = EV200_EVT_CATEGORY from EV200_EVENT_MASTER table

    We would also like to UPDATE Attendance = EV200_PLN_ATTEND and Actual Attendance  EV200_ACT_ATTEND (currently these are stored against Opportunity Types - Event Sales ZZ Default Event UDF Set - CR158_ISSUE_MASTER - CR158_ISSUE_TYPE =  Z3 and CR159_FLD_DESC = TXT_01 (Anticipated) and TXT_03 (Actual)

    We would also like to use fields not used before and still to be setup in the Event Seasons and Event Series into the EV200_EVENT_MASTER, but I believe we would need to join that table with CORE_EVENT_SEASON_SERIES EVENT_SEASON_ID and CORE_EVENT_SEASON_SERIES table.

    My concern with this last one here is I believe this might require a SQL script (which Momentus would need to run, as the CORE fields aren't available in the EV200 data model, therefore they don't seem to be available as API ENDPOINTS to update)

    Could you please confirm what the best approach would be? Would this be using the API, an SQL script or a combination, also we are mindful that the historical events would have fields like Event Category already posted via GL Journal Entries.

    If possible, we would like to discuss this request with Professional and Tech Services team to ensure we fully understand any limitations or conditions around what the Olympia team would like to do, which is for improved reporting.

  • Mike Schepker

    Francesco Torchia This seems outside of the scope of support and would need to go to Tech Services or Consulting. 

  • Francesco Torchia

    Thanks, Mike Schepker 

Please sign in to leave a comment.

Didn't find what you were looking for?

New post