Hi, does anybody has experience on Web Part chaining and know how to
handle this situation?

Thanks!


On Jan 31, 7:01 pm, "Ivan" <ivany...@gmail.com> wrote:
> For any pair of connected web parts (provider, consumer), the provider
> side is connected first, then the consumer side, this makes sense in
> general, if the provider and the consumer are 2 different web parts.
>
> But for a single web part that implements both a provider and a
> consumer interface (a type of in data processor, then output), this
> ordering is not good, since this single web part should only output
> (provider) when input (consumer) is available. All the examples I
> have seen so far, they bundled the step of web part connection, and
> data transfer together, i.e. data transfer is always done inside the
> PartCommunicationMain function. I think this is due to the connection
> and the data transfer are really happening together on the server
> side, even though logically they can be thought of as separate steps.
>
> My objective is to only fire data ready when my single web part has
> consumed some data. However, with the SharePoint infrastructure
> always calling the provider side first, how can I achieve this?
>
> Any advice is highly appreciated!