Use BPM to set Default Report Style

Kinetic 202X
,
1

Hi All,

I have some custom report style but when I port in using solution workbench the Default setting for that custom report style is not ported in as well. Right now, for each custom report style I would manually go to the Report Style Menu and manually enable the Default for the custom report style.

I notice that it uses the Ice.ReportDefaultStyle table and I wanted to do an updatable BAQ to make it easier to enable the default but the table is not available in BAQ.

Then, I notice there is a ReportDefaultStyle in the Data Directive but I’m not certain how to have it call from ReportStyle to set the default.

Anyone has any idea?

Warm Regards,
Mei Mei

2

You are correct. I always had to provide additional post-deployment instructions such as:

image
image770×724 139 KB

But since we are on-prem I shifted to providing a SQL Update Statement which sets the defaults, I havent tried DMT or a UBAQ Dashboard.

2 Likes
3

Would Epicor has issues with the SQL update though? I usually sticky to BAQ updates because of how Epicor support can be if you mess on the SQL side?

4

It’s a very valid concern @Mei_Mei_Tan , just not for @hkeric.wci

5

We do SQL Updates to any tables that are low-risk… I wouldnt do an INSERT or a DELETE, or even change a PartNum. Typically I review in-depth what the column is or does… Example Ill do what I want with my _c columns… When its a column like changing the Menu Arguments, ill do SQL, DMT or UBAQ, or LINQ in a BPM.

TLDR; It depends what I am touching, 99% of things I dont touch via SQL. However this one I do because there is no way to auto-deploy this using DevOps unless you include a SQL Script, due to Epicor Solution limitations.

Also Epicor Data Fixes are just SQL Statements in an sp, they just vet what they do and they take on the risk if they mess up your database.

4 Likes
6

Okay, thanks! That’s good to know :smiley:

2 Likes
7

I am pretty sure this used to work on E9… I have to say it is annoying.

1 Like