Editing a Stored Procedure - adding a field

I was wondering if anyone had any advice on resources for editing a stored procedure. I just need to add a field to a report that is driven by a stored procedure. I see that I can extend the IDO, extend the IDO Method and add the columns, but do I also have to extend the SP and if so that is where I am lost. Is it something I can do through Infor/Mongoose or do I have to do it in SQL?

Find more posts tagged with

**General Discussion**

Accepted answers

All comments

kazuyuki-mochizuki

Easiest way I see is an unbound and add the column/value thru the front end (reportviewer)

0905290750040159.pdf

unknown

If you are only adding a field for a report, I would look at the derived fields in the IDO. you can use sudo sql there (replace column names with property names)

Every time the IDO is called, the sql for the derived field gets run. So any call at all including reports will get this field. So you would add a new property to an extended IDO, select the derived option. and fill it out from there.

I am not saying this is a great example, but I hate to leave you with nothing so maybe this will help.

If you open the IDO Properties form, select the implementation tab, and enter something to search for something like *case* you can then un filter and see what INFOR has in there. This helped me a lot while learning this.

This wasn't covered in the training as thoroughly as I would liked it to have been as it has proved VERY useful for me.

Ryan Pukanski

You can just add the collections where the field is on the report viewer form.

This way no IDO or SQL editing is required.

mtolliver

This is the route I started on, and it worked on 4 different reports for me. I'm just trying to add a field from the Items table to all customer and vendor facing documents. When I got to the QC VRMA Packing Slip, for some reason it is giving me a report creation failed error. I have validated over and over the correct case and spelling of the properties. Its hard to mess up since it is just Item = FP(Item) linking the SLItems ido to the QC VRMA Packing Slip Report. It's very frustrating that it was working with every other report and not this one, so I figured I could try and go the complicated route for this one only.

mtolliver

as soon as I add this - it fails

Ryan Pukanski

Do you have the item field from the SLItems secondary collection 2 on the report somewhere? Have to add that in and then hide it if not required to be seen otherwise its not bound correctly.

What's the exact error you get in bgtaskhistory? I've seen a couple errors with this method as well.

mtolliver

Thanks this is helpful - I will give it a shot and see if it works for what I'm trying to do now, if not this is good information for the future

0911060553270289.pdf

Ryan Pukanski

Have you tried this for custom load method IDOs? I don't think derived works on those. I tried years ago and I had to get an enhancement put in to get support for it. The code to do the derived SQL is not called when a custom load method is specified. The enhancement did get approved so maybe its live now. I haven't tried in a while.

unknown

Does the Background Task Exceptions form give you any more information on the error?

Copyright © 2025 Infor. All rights reserved.