All of the user guides and educational videos talk about how UD Fields are available for most forms for Public Cloud customers (you do not need to add columns like you do for on-premise). I am trying to add a couple of UD Fields on Customer Maintenance. When I try to find the EpiBinding field, I do not see anything that looks like a UD field under the Customer folder.
However, when I look at the CallContextBpmData, it looks like there are a bunch of UD Fields.
Are the CallContextBpmData fields the UD Fields that I should be EpiBinding to my epiTextBoxes?
For me it’s the same process as on-prem. You do UD Field Maintenance and then submit a request to the Cloud Team to rebuild the Data Model. Once they finished that - which requires a restart of the app server so your users will get bounced, I see the myFieldName_c in the table added to in the EpiBinding fields.
Epicor used to ship with those generic UD types but those are not related to UD Column Maintenance.
You won’t want to use the CallContextBpmData for this. It isn’t what you may think it is.
The Customer table on the MT SaaS should have a number of fields already created. The fields would still be things like Character01, Date15, ShortChar04, etc. They don’t create custom named fields on the cloud…
Jason,
Thank you for the tip on NOT using the CallContextBpmData.
I have searched the Customer table (under the drop down for EpiBinding) and the UD Fields you reference do not appear. I have attached a snip of where the Character UD fields should show up under the Customer table.
There are no UD fields in Customer table unless you specifically add some. Did you add Custom Fields in the Customer Table?
IF you haven’t you need to create these in the UD Column Maintenance form. I would highly recommend you do not called them Character01 and Character02… but rather the real names based on what you’ll be storing in them.
This is what lead me down the path (because we are a public cloud client).
I will follow your advice and I have gone through the steps to add these columns in the UD Column Maintenance. Now I still need to put in a ticket to “Regenerate the data model and recycle our application pools”. After that happens, if I need to change any of the individual settings on these new UD columns, will I have have to put in another ticket to Regenerate and Recycle again?
That’s was more true in the Multi-Tenant days but for Public Cloud (formerly Dedicated Tenant) this is the new normal. The hope one day is that several of these kinds of items will make it to a portal that the user can initiate when desired. Start with restarting task agents, then copying live to pilot, then a Data Model Regen, and eventually - for Flex users - the option to begin an upgrade.
Well, no. Public Cloud is the new name for Dedicated Tenancy. Single Tenancy is more like Infrastructure as a Service (IaaS). Epicor manages your VMs in a data center and not necessarily in Azure. In ST, YOU have to do your own Epicor upgrades and patches unless you pay Professional Services or some other company to do them. Epicor does the backups, Windows & SQL Server patching. If you do RDP to the servers, there’s a per user account/month charge. So it’s in-between On-Prem and Public Cloud.
