Feed

unable to select the option as it not displaying any pop up in 

1. Become an Agentblazer Innovator 2026

1.  
2. Service Agent Customization with Prompts, Flows, and Actions

1.  
2. Update a Flow, Agent Action, and Subagent

I am using trial org with omnistudio inbuilt and hence on standard runtime. I am not able to import the omnistudio related packages in my .js file , for example import OmniscriptDate from 'omnistudio/OmniscriptDate' gives error to me.  

I have a requirement to use a custom lwc for a date validation, now I am able to the validation perfectly but not able to pass the data from LWC to omniscript. I have tried Custom events as well. Below is the code snippet: 

    sendValueToOmniScript(valueToSend) {

        console.log('sent value1',valueToSend);

        const payload = {

            elementId: 'SinceWhen',

            SinceWhen: valueToSend,

            omniJsonData: {

                SinceWhen: valueToSend

            },

            SinceWhen: { value: valueToSend }

        };

        console.log('payload',JSON.stringify(payload));

        this.dispatchEvent(new CustomEvent('omniaggregate', {

            bubbles: true,

            composed: true, 

            detail: payload

        }));

    } 

Hi Trailblazers,   

we're in the middle of implementing Data 360 and Marketing Cloud Next, and while setting up our data streams we've run into a problem that someone here has hopefully seen before.

All field labels coming through on our data streams are displaying in German instead of English. This happens regardless of the individual user's language settings: even when your own profile is set to English, the fields still show up in German. After some investigation, this seems to trace back to our Hidden Platform Integration User, whose language is set to German. The data streams appear to inherit the labels in that user's language.   

This matches the behavior described in this known issue article: https://help.salesforce.com/s/articleView?id=001859649&type=1   

Affected:

• All standard fields
• All fields from the Nonprofit Success Pack (NPSP)

A few constraints that make this harder for us:

• We can't change the Platform Integration User's locale. As far as we can tell, it's set once when Data Cloud is initialized and can't be changed afterward, so fixing it at the user level doesn't seem to be an option.
• We can't delete the affected data streams. The streams on objects like Contact and Account were installed via the Sales Data Kit, so the delete option isn't available, and attempting to undeploy throws an internal server error.
• The org is essentially in its initial state. We have no Identity Resolution rulesets and no Calculated Insights active, so there are no downstream dependencies blocking us from making changes. However, because the data streams were installed via the Data Kit, we also can't remove the field mappings, so adjusting the mapping isn't an option either.
• We plan to add more instances later. The intention is to connect additional instances down the line, so it's important for us to understand how this issue plays out in the medium and long term if we leave it as is now.
• We can't grant Salesforce Support access to the org. Our client's security rules don't permit support login access, so any solution has to be something we can carry out ourselves.

Since the org is basically still empty, we're open to more drastic options too, such as reinitializing Data Cloud or rebuilding from scratch. So we're happy to hear both targeted fixes and clean slate approaches.   

A few questions for anyone who's hit this before:

1. Has anyone found a way to correct the integration user's language/locale after Data Cloud has been initialized, or confirmation that it genuinely can't be changed anymore?
2. Did the labels on existing data streams ever update through some other means, or do the streams have to be recreated or refreshed to pick up the corrected labels? And if a rebuild is the only path: how did you handle the Data Kit streams that can't be deleted?
3. Has anyone successfully worked around the Data Kit undeploy "internal server error" without involving Support?
4. Given that the Data Kit locks the mappings, is there any fix at the data stream or DLO mapping level that avoids touching the integration user entirely?
5. What are the implications of leaving the current state as is, especially given that we want to add more instances later? Are there issues that only surface at that point, for example with Identity Resolution, mapping, or consistent naming across multiple instances?
6. Specifically for anyone using NPSP: are there additional gotchas with the field labels from the managed package?

We'd really appreciate any experiences, workarounds, or pointers to official documentation.

Thanks in advance!   

@* Data 360 *