Understanding the Extend with the "Replace" option.

I can see that there is a "Replace" option that is applicable to Extending an IDO, and also when Extending a Form.

From what I am reading, when you select Replace, the new IDO or Form is used in wherever the Base IDO or Form would normally be used.

This seems like a better way to customize a form within a "Canned" application (where you are not the vendor).

So, my question is, if the application Vendor releases an upgrade, and you apply the upgrade, how does Mongoose apply those changes to the "Replaced" IDOs & Forms?

For example, if I add code to the Form Class so that I can create an Event Handler and have it execute the code in the Form Class, and then the Vendor makes changes to the Form Class of the Base Form, how does my Form Class custom code get integrated with the Base Application Upgrade?

Thank you for your thoughts.

Regards,

John Keegan

Find more posts tagged with

Accepted answers

Legacy Contributor

The feature is pretty new, so I am going to guess you are probably hitting a bug. I'd report that to Infor so they add it to their list. As far as reverting goes, to permanently revert, delete your extended form, and the base form will again be the default. For a temporary solution (to view the code/copy paste it into an external editor) change your user editing permissions from Site Developer to "4". Then log out and back in. You will then be using the system in Vendor Default mode and no customizations will show and you should see the Base form instead of the extended one. If you wanted to edit one of the base form functions, I believe you would copy the code into your extended form (keeping the same name and parameters) and yours should execute over the base version.

All comments

Legacy Contributor

According to the tech briefing we just had with Infor, the new extended version of the form you create is a differential copy of the base form. That means the extension only contains the changes you made, it gets the rest of the form bits from the base version.

When an upgrade happens, it upgrades all of the base bits but you get the changes in your extended form for only the form bits you didn't change. During the Form Sync process, you'll get messages about whether to keep or discard your extended changes. In the case of a change to an IDO Method Call signature, you will have to manually merge the changes into your extended version (add the additional parameters to the method call).

Not too many people are doing it yet, so there isn't a whole lot of real world experience to say what works and what doesn't yet. Our rule of thumb is, if it's minor changes to a form you are doing, do an extended form. If it is major rework, make a copy of the base form.

Legacy Contributor

I have developed the sample extended form.

I could able to modify the components properties and event handlers by changing the property called "From Base".

But my question is,

if i want to modify the existed form script which should affect only in the extended form (not the base form script), then what i could do,?

Because in the extended form, there is no form script showing of the base form.

Please let me know how do i do this?

Legacy Contributor

Thanks Tim!

I've done some testing, and here is what I have found so far.

I have created a new Form extending and replacing the "NonconformanceMaintenance" form.

As per the documentation, my new form (the "ausNonconformanceMaintenance" form is kind of a Copy of the NonconformanceMaintenance Form with ALL of the Components on the form LOCKED that somehow refer back to the Base Form.

The way I can edit the Components is to change the "From Base Form" property from TRUE to FALSE. I can then edit the Component.

Also, when I look at the Form Script code, all of the original code from the Base Form is missing, and I have a template for adding code to the class: "ausNonconformance : vqNonconformance" (on the base form the class is: "vqNonconformance : FormScript).

I am assuming that I can just add my form script to my extended form class definition, but I am seeing some symptoms that worry me.

Whenever I try to call up the base form, because I selected "Replace", my Extended form starts up (by design I suppose). So I can't access the Base Form Script code anymore. It seems that once I created the Extend / Replace form, there is no turning back.

Before extending the base form, there were "User Defined" labels (Statics on selected Edit components) that were changed to custom values, defined by the sa user in a "User Defined Label Maintenance" form as part of the application.

Now, after extending the form with no other edits, that feature no longer works. I suspect that there must have been some Form Load Event code that changed the Statics to the custom values.

The Application, by the way, is Infor Quality Management / IQM.

Shouldn't the Base Form script be working the same way it did before the Form was Extended/Replaced?

I apologize for the long post.

Thanks for any thoughts you might have in this matter.

Regards,

John Keegan

Legacy Contributor

Thanks again Tim!

I have submitted this as a bug to Infor Xtreme, but have not heard back from them. For now, to keep my project moving forward, I have created Extend / Replace IDOs of the IDOs that appear on the Base Forms, and then edited the base forms on the Site Level.

I know now that if I upgrade the application, I will have to re-apply the form customization again. Hopefully, Infor will have fixed the bug, and when I do upgrade next, maybe I can re-do the customization on an Extended / Replaced form.

By the way, you mentioned that you had a Tech Briefing with Infor. Is that a bulletin that Infor sends out to subscribers? Or do you have a formal relationship with Infor that gives you access to the Mongoose team at Infor?

I don't mean to be nosy, I am just looking to understand what resources are available to me regarding my Mongoose development efforts.

Copyright © 2025 Infor. All rights reserved.