Yep, just add it.

ACC doesn't tolerate corruption at all in objects, and will gray out the UI when it's detected. AFAIK [view/eventDate] is not an ootb field, so delete and recreate.

Did you change it to ==?

Hi, Does it say dataSource.Job_Category =="Corporate" or dataSource.Job_Category ="Corporate"? Thanks,-Jon

Hi, This is by design. Two workarounds:Change your js to read the real query string instead of the pseudo query stringCreate a page or jssp that re-redirects, transforming query string params to pseudo-qs params, then link to that instead Thanks,-Jon

Hi, Are the deliveries referencing proof groups that weren't copied to Staging env? Thanks,-Jon

Hi, You could alter the landing jssp to show hints, or add a new tab to it for a best practices page.Past that it would be static fields in forms, though that could negatively impact usability of the app. Thansk,-Jon

Hi, Was this what happened?The nms:offer schema was altered to include a new field, [view/eventDate]An offer space was edited to reference that fieldThe schema was reverted, with the reference left in place If so, just delete the bad offer space from design and live env and make a new one. Thanks,-J...

Hi, It depends on what you want to do:Show/hide anything in UI: navigation hierarchy, formsControl access to API calls, functions: HasNamedRight() in js, jsspShow/hide data cols: enabledIf/accessibleIf in schemaShow/hide data rows: sysFilter in schema Thanks,-Jon

Hi, Are you asking about Campaign Standard?https://docs.adobe.com/content/help/en/campaign-standard/using/administrating/configuring-channels/configuring-a-mobile-application.html Thanks,-Jon