I ended up just deleting and re-adding the tab and the number started to show up. I know a List View tab is required for this. The initial table you link to is very important (when you add the first field - it will link that as the primary table), and if that is done incorrectly, it could cause weird behavior.There is some more information on the user documentation that lays this out.
Thank you for the response. I can definitely see the merit in this response, but I don’t think is the best solution in our case because we do need communications to go out for the purposes of testing email and text communications as well as integrations.I think we are going to go down the route of writing a query to automate a lot of this through app params and routing rules.
This would actually add a step instead of just manually deploying since I would still have to copy and paste all the fields. This solution would just require the extra step of importing it on all those tables. I was hoping for a solution where I could include it into a deploy package to deploy with all other requirements into our production environment to reduce human error and extra deploy time.I have tried to use a SQL change to put them into a package (which they show in there in the interface), but it wipes everything and just leaves what is in the current package.May I ask why these items are not able to be added to a deploy package, especially when you can put the child records into one?
Unless I am missing something, I am looking at my package extract settings right now and for sure you can not put DISTR_LIST, NOTIFICATION_MESSAGE or substitution maps into a package deploy.You can put DISTR_LIST_MEMBER and WILD_CARD_MBR_REL into deploys, but those are sub sections of the above items.This means we have to write down to manually deploy in all environments which creates a huge room for error, as we have experienced in the past and have had production bugs from it.For Global Codes, let's take DISTR_LIST for example. You can deploy the whole table or nothing. We have multiple engineers doing different things. The only way for this to be viable is to compare to production. If the only global code to be added is missing from production, then we can deploy. Often, this is not the case. What I am asking is why can't I deploy just one DISTR_LIST_MEMBER instead of the whole list?
The CSV integration map includes quotes around each line. This is not the case with a Flat File map. So creating a Flat File integration and switching over all the components to the new integration map will resolve the issue.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.