Answer
First, double-check the field is actually published, not just saved — an unpublished custom field won't appear in Aurena regardless of its Visible setting. If it is published, check the grid's own column configuration next: open the hamburger/three-lines menu on the list/grid and use its 'configure columns' option to check whether your new field is available there but simply not enabled in the currently displayed column set — a field being Visible=true at the definition level doesn't automatically mean every grid shows it by default; it may still need to be manually enabled in that specific grid's column list. If the field still doesn't appear after checking both of those, use the Debug Console to check exactly which underlying view that specific list is actually querying — some lists pull from an additional or different view than the one you published your custom field to, in which case the custom field needs to also be published to that specific view for it to appear in that particular list.