People Planning Register Field Data Not Populating

jpray
New Contributor II

I have loaded test data into our PLP Register. 2 of the individuals have been given a Promotion Amount and a Promotion Period in |NCode1| and |NCode2| respectively. We've imported values in both fields via a template. Although the fields in OS are not populating the imported data for this Register Field, it has been imported properly and tested successfully. (see screenshots below).

Need: Assistance with finding a solution to have the data properly show on the register. 

Below are screenshots of:

1. Register in OS PLP showing blank cells (even though the data/Promo Periods are active and successfully tested)

2. Register Field List showing which Codes we are using as well as validation the Parameter is successfully used elsewhere

3. The Import Register Template with data in fields

4. An Export of the Register from PLP showing the data exists

jpray_0-1661618310781.png

jpray_1-1661618353864.png

jpray_3-1661618614369.png

 

jpray_2-1661618574626.png

 

 

1 ACCEPTED SOLUTION

your value must be SqlTypes.SqlDecimal.ConvertToPrecScale(SqlTypes.SqlDecimal.Parse(decimal that shows in the drop down), 28, 9)

View solution in original post

5 REPLIES 5

You cannot use those as parameters. You'll have to use them so that they recognize those as SQL decimals. I thought I wrote about this somewhere. Let me llok

It is in the OneStream Planning book Page 179.

your value must be SqlTypes.SqlDecimal.ConvertToPrecScale(SqlTypes.SqlDecimal.Parse(decimal that shows in the drop down), 28, 9)

jpray
New Contributor II

I made changes based on your successful solution, thank you!

Interesting, it must be a decimal and is not allowed to be an integer given both of those would seem to fit |NCode|

NCode is stored in the SQL Table as a decimal(28,9) datatype, and that is the reason why you'll have to convert it. It is successfully stored in the table as a decimal (even though you loaded an integer). However, when it now tries to show the drop down, the values and the display are all integers and it cannot now show the display value associated with the decimal.