Warning in disabled control Container
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Im finding an issue with control containers that if i have a Append tool inside it even if the control container is never activated it gives a Warning of:
"Warning: Append Fields (190): There were no records present in the source".
Any ideas how to avoid this warning?
I attach a sample workflow to replicate the error.
- Labels:
- Workflow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Not sure I understand the question - if the control container is disabled, the warning doesn't show. If it's activated, it shows. This is the expected behavior!
Control containers just execute tools in the order you put them in - it doesn't turn off the container entirely if you have no records
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
No, I don’t mean a hard disable. What i mean is a control container that is not activated. In the attached workflow try 2 scenarios, one putting the count = 2 and one putting the count filter = 3.
If you put count = 2 then the container is activated, and everything works ok.
If you put count = 3 then the container is not activated and a tool that is inside there gives a warning (when it should not run).
Warning: Append Fields (5): There were no records present in the source
Thats the warning I want to avoid.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Interesting - I am not sure of the best answer then. I would look at using the Detour Tool (alteryx.com) possibly to help!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
The control containers unfortunately are just buggy with many tools. I think that the behavior for enabled verses disabled containers is not the same as the behavior for activated/deactivated containers but we expect it to be the same as we our building our logic.
I had wanted to use a SharePoint Input (2.4.1) tool inside of a control container, and everything works fine when the container gets activated by my logic, but if the enabled contain gets deactivated (by the filter connected to the Control Container input anchor) then the SharePoint tool which should not be running gives an error.
![](/skins/images/59DA3CA97FC6306BFE8B6DED203F3AC0/responsive_peak/images/icon_anonymous_message.png)