Category Archives: Extender

Extender Fields & Report Writer – Weekly Dynamic from Mark

Posted on by

Those who want to know how to add/use Extender Fields on a Report Writer report, Mark’s Weekly Dynamic post, Extender and Report Writer walks us thru’ simple steps with a real time scenario.

There are also links to relevant KB articles which will form the base for your task.

VAIDY

Display Extender Data for GL Trx Lines on GL Inquiry – David

Posted on by

This post is awesome. And quite a practical requirement nowadays. David takes us thru’ the steps involved in writing a piece of code that does wonders for us.

Read it here: Display Extender Data for GL Trx Lines on GL Inquiry

VAIDY

VBA – Adding Extender Windows to GL Transaction Entry Lines : David Musgrave

Posted on by

This is another code wonder from David Musgrave.

A Hybrid approach (VBA & Dex) which solved a GP – Extender issue. Read it here: VBA – Adding Extender Windows to GL Transaction Entry Lines.

A Must Read for GP Developers.

VAIDY

Why Extender Information does not get transferred?

Posted on by

I have been getting this query on WHY EXTENDER INFORMATION ON A SOP QUOTATION DOES NOT GET TRANSFERRED TO THE CORRESPONDING ORDER?
Well, there is obviously no logical reason behind it. Given the fact that SOP User Defined values are getting transferred from Quote to Order to Invoice, we expect the same thing from Extender Information also. Point substantiated.
But why Extender Information does not get transferred? There is a technical reason behind it. Extender Information is created based on the Key Fields that we are setting up in the Extender Window/Detailed Window definition form as shown below (COLOR BLUE BOX):
Most of the times, when a Consultant / End User create an Extender Information Window (or Detail Window) for an SOP Document, the Key Fields are typically “SOP Type” and “SOP Number”. When the user enters some information for an SOP Document, Extender saves this information in it’s table for the Key Value . For instance, if your SOP Document Type is Quotation, then SOP Type is 1. And if your SOP Document Number is STD-QT-123456, then the Extender Key Fields combination is:
STD-QT-1234561 {Last character “1” stands for SOP Type Quotation}.
When you convert this Quotation to an Order, a new SOP Document Number and SOP Document Type is created. For instance the above Quotation may get transferred to an Order of SOP Type 2 and SOP Document Number STD-OD-333333. Obviously for this SOP Order, the Extender Key Field combination would be:
STD-OD-3333332 {Last character “2” stands for SOP Type Order}
Extender does not understand the new Key Fields combination and it does not show up when you open that Extender Information Window (or Detail Window), as the information for the Quotation is for different Key Fields combination.
Hope the above explanation is clear.
Now, you may ask me another question: GP also does the same thing. Converts a Quotation to an Order with different SOP Type and SOP Number, but it still retains the SOP User Defined values. Why can’t Extender do the same thing?
For that query, I do not really have an answer both technically and logically.

But for now, that’s how Extender works.

UPDATE: You can’t really say that this is Extender’s drawback. Simply, Extender is a generic Addon for GP, which leverages the functionality. Having said that, Extender people cannot really write a specific code like what I explained above. Which does not make sense for developers to release a product with such process specific code. Moreover, Key Fields combination on SOP Documents can be anything along with SOP Type and SOP Number. Sometimes even without that. We really don’t know. Now, read the remaining part of this post.

For All Consultants out there: Be very clear on this point and design your solutions accordingly. Make sure that your Customers understand this point as well.
Let me not end this article on a negative remark.
Extender does give us a beautiful feature, which is Extender Inquiry. This makes sure that when you post a transaction which has an Extender Information, it is also shown when you inquire that transaction. And best part is that, you can either edit it even after posting or you can keep it Read-Only.
Nonetheless, Extender IS a very good tool for all Customers out there. It’s us Consultants, to decide on how effectively we are going to utilize it for Customers’ needs.
VAIDY

Creating Detail Window in Extender – Error & Resolution

Posted on by

I am working on Extender features after quite some time.

I was creating a Detail Window for Service Call Entry/Update window in Field Service. I entered Window ID, Description, Product, Series, Form & Window. I selected a Key Field and entered one Line Field.

I tried saving the Detail Window and I got this error message:

Certain Extender features and data may no longer be available with the installation of this product. It is recommended you reference your product manual before continuing.

I was quite puzzled to see this message as this is conveying something more like, I am not suppose to create a Detail Window at all. Or probably I perceived it in that sense.

I thought I would check KB before I conclude my defeat. I found a KB article which addresses this exactly: KB#947934.

My mistake. I did not select R1 or R2 for the Line Field that I tried creating. Obviously, we must specify whether the field which we are trying to create should be in first line or second line. And if we do not specify, Extender does not understand and create it automatically.

Having said that, the Error Message could have been a bit relevantly meaningful.

VAIDY

Removing Extender Records – David (Critical Reference)

Posted on by

We all owe a lot to this guy, for timely and qualified solutions that he provide.

We have been facing this issue long time now. When we delete a Parent Transaction, the dependent Extender Information is orphaned and we do not know that. Over a period of time, this gets accumulated and lots of junk.

David nails this issue with his solution. Read it here: Removing Extender Data When Deleting Transactions or Lines.

This is very critical reference and we MUST treasure this. And I sincerely mean it.

VAIDY