Forum Discussion

KH1's avatar
KH1
New Contributor III
8 months ago

DM Export Sequence: DMES

https://community.onestreamsoftware.com/t5/OneStream-Tech-Talks-Continue/New-Episode-of-Tech-Talks-Available-Now/td-p/33894

G'day,

In this Tech Talks for Data Movement, Nick Bolinger suggested to use DMES as a better way than a DM Copy Job to copy data between S#s.

We Imorted Actuals for '21-'23 via a Yearly Matrix and S# to then use a DM Copy Job to copy the Base data to a new Monthly S#Act: '21-'23 + '24.
Pls share your DMES expertise to help us better copy Base data from historical Yearly S#Act's T# ('21-'23) to those T# of a live Monthly S#Act ('21-'23 + '24).

TY.

  • chul's avatar
    chul
    Contributor III

    Sounds like your data doesn't line up if you're going from a yearly input scenario to a monthly input scenario. You'd likely be better off using a business rule if you need to do math to break down the yearly amounts into monthly amounts.

  • KH1's avatar
    KH1
    New Contributor III

    G'day Chul,

    Imported Actuals for '21-'23 via a Yearly S# under a Yearly Matrix of Monthly data.
    - DM Job for '21-'23 took hours to Copy millions of records to a live S#Act.
    - DMES and other solutions is more performant than DM Copy Job per what I heard from Nick Bolinger in the Tech Talks.

    TY.