Function that allows to enter a number in field and then this can automatically be populated in all

Hi Community,

I am looking in application studio a function that allows to enter a number in a field and then this can automatically be populated in all columns of the same row as same as the “Data Entry Basis Rates” report does.

Someone has experience what is the best practice to do it? My goal is avoiding retyping same number twelve times in my custom reports. I appreciate your comments?

Regards,

Mauricio

Find more posts tagged with

FAQs, How-To's, and Best Practices

Comments

Nick Gladkov

you can have it two ways, I would say (at least). First - if it is common rule for each year for this measure - just put it on the '-'/'NA'/'Any other period' Time element and have OLAP Rule that it puts values to each month.

Or use Splashing and AppStudio action, in this case it will be "#B"&AppStudioCellCoordinate (for instance "#B"&C3). Here is a bit more about Splashing usage - https://docs.infor.com/depm/2022.x/en-us/depmolh_cloud/default.html?helpcontent=application_studio_cloud/boj1510174447568.html&hl=splashing

John Robson

Where there is a natural parent like Year my preferred method is to use an Application Engine process to write a value to each base element. with a very simple process like the one below using OLAPSetDataAreaValue. An edited cell action can trigger it. You would likely need to pass in more parameters.

This is a sample - with hardcoded elements from the Best Practices Analysis Cube.

#define EngineVersion 5.0
#define RuntimeVersion 5.0

bool CubeSetDescendantValue(string application, string cube, string pertop, double valueNew)
@Parameter[application]: "Application e.g. BestPracticesOLAP";
@Parameter[cube]: "The cube to write values to e.g. Analysis.";
@Parameter[valueNew]: "The new value to be written e.g 22.0.";
@Parameter[pertop]: "The time element e.g 2012. The process gets all base elements under this parent.";

@Description: "Sets cube values to the specified parameter value.";
@Category: "Utilities";
@Returns: "True - always";
{
    //Version 2 - John Robson 19-July-2022
    OLAPConnection OlapCon1 = OLAPCreatePooledNamedConnection(application);
    OLAPElement perpar = OLAPGetDimensionElement(OlapCon1, "Period", pertop);
    OLAPElementList PerList = CreateOLAPElementList();

    //Values should be base elements
    string POS = "Bodyshops";
    string Product = "S8000/245";
    string Region = "Angola";
    string Channel = "Direct Sales";
    string Measure = "Units";
    string ValType = "Budget";

    PerList = OLAPGetChildElementList(OlapCon1, "Period", pertop, true);

    OLAPDataArea cubeVals = OLAPCreateDataArea(OlapCon1, cube, OlapDataAreaIncludeB, OlapDataAreaOperatorNone, 0.0, OlapDataAreaOperatorNone, 0.0 ,PerList, POS, Product, Region, Channel, Measure, ValType);

    if (valueNew != 0) //Assume user doesn't want to write a zero and instead clear the Data Area
    {
        OLAPSetDataAreaValue(cubeVals, valueNew);
        WriteLine("New value set.");
    }
    else
    {
        OLAPDeleteDataArea(cubeVals);
        WriteLine("Clearing data.");
    }
    return true;
}

Mauricio Mendoza

I appreciate your comments. Thank you, John, Nick.

Copyright © 2025 Infor. All rights reserved.