Hey @Anuhya-Y  Here is the correct body to create Cross-Channel Fragments{ "name": "Cyber Monday Sale - Header !!", "description": "Cyber Monday Sale - Header Banner!!", "type": "expression", "source": { "origin": "ajo", "metadata": { } }, "fragment": { "expression": "Hi {{profile.person.name}} its ...

 If I change the type to expression it also doesn't work in the API.  

If I do this, it will generate a fragment that only works for emails and not cross-channel

Im trying to the create cross-channel fragment by using APIs, but Im getting this error Body:  { "name": "Cyber Monday Sale - Header !!", "description": "Cyber Monday Sale - Header Banner!!", "type": "html", "channels": [ "shared" ], "source": { "origin": "ajo", "metadata": {...

Thanks, exactly So if you check in the schema this 64-character limit is not present for the field treatment name I was trying to look at other field limits but it seems like there is no limit establish

In that section an error pops up and doesn't save,  Please save it with the correct name and then go to edit the email,  on the left side of the screen the you will see 2 treatment names, try to modify from there but it is not working 

If I check by treatment name it mentions no limit But when I fill in the title I see there is actually a limitso this is information is not really matching

Hey @DavidKangni Sorry, but Im actually looking for the character limit when you create an audience in AEP or you create a Journey/Campaign   

We are setting up some internal naming conventions and Im not able to find any limitation in terms of characters length for the following Journey NameCampaing NameDelivery/Action NameAudience Name For exampleTreatment Name -> 64 Characters Limit

@MrMAK coming back with something that might be better for you. Do you have this dataset available on your end? JOJourneyVersionsDsThis dataset contains all the details you are looking for