You are viewing this site as a guest. You can still ask questions and help others! Join our Dev2Dev IT Community to receive your own blog, share your knowledge, and much more.

CI limiations question

1 reply [Last post]
Guest's picture
Guest

Hello,

I understand, there are a few limitation on invoking a component thru a CI. Primarily:

1. Save edit/init are not called.
2. do modal do modal component are not called.
3. dosave/dosave now are also not called ?

Has any one worked to circumvent the above limitations ? If so , how was it accomplished.

For e.g. I believe, one could create a wrapper method to do it. Can someone share the implementation. For e.g. where will this method reside and how and when it will be called ?

CompShack's picture
User offline. Last seen 5 years 41 weeks ago. Offline
Joined: 12/09/2007
Posts: 167
Re: CI limiations question

The limitation is when you write PeopleCode for a component interface. SearchInit, SearchSave, and RowSelect events will not fire also. DoSave() and DoSaveNow() are not called as CI uses the save() method instead, so they are not needed. I have not heard of a work around for these limitations. I don''t know how would you even want to do that? You should actually wrap the DoSave() and DoSaveNow() functions for components that have CIs so they don't get executed when called by them. You can uses %CompIntfcName function to accomplish that. The function will return the name of the component interface that is calling the Peoplecode, and it will return NULL if the code is not being called from a CI.

Give back to the community and help it grow!
* Help with unanswered forum questions and issues
* Register or login to share your knowledge at your own blog