Good morning - I'm trying to remove the Dunning bu...
# general
b
Good morning - I'm trying to remove the Dunning bundle fields from our transaction forms. We've never used Dunning, and don't get me started on why it was ever put installed in our Production account even thought we determined during implementation that it didn't fit our Business needs. Anyway, if I remove the Dunning tab from the form, the tab goes away but the fields get thrown on transaction body. Is there a trick to removing the fields and the tab? Is it because the fields are locked from an installed bundle? This is what happens when the tab is removed:
We've been told that it's risky to uninstall bundles - as far as unintended impact. And the Dunning bundle is huge in the number of fields, workflows, and scripts. If we ever have time to actually test that in our Sandbox we may do that. But we always have so much going.
t
Can you customize your transaction form and remove all of the transaction body fields that you don't want?
message has been deleted
b
I spent hours yesterday trying but am just looking at it again - I think I finally figured my issue - thanks!
Nope - false alarm. Spoke too son. The only way I can do anything with those fields is using
Move Elements Between Subtabs
- and that only allows moving the fields from one subtab or subtab group to another. And hiding the subtab or group just throws them elsewhere on the form. For now I'm going move the subtab to the end.
t
Have you tried unchecking the Show box?
b
Yes - that's what I tried a little while ago when I thought I figured it out. But they still show up. I'm hoping I'm just missing something.
t
Hmm. I've never seen that before. I'm not an expert but I wonder if this bundle is overriding this.
b
That's what I'm thinking.
s
Turn off all of the dunning workflows as I believe one or more of those controls the fields that you are seeing. You should turn them all off anyway.
b
oh thanks - I hadn't thought about that!
@Simon Whittle - thank you so much for the hint. Turning off the dunning workflows solved the problem!
s
Glad that worked