@Erika_Antkowiak  it is possible using schema editor which allows drag/drop for the field but only possible with in same metadata schema not from one schema to another.

@Rucha_Supe  @Rucha_Supe  did not find as well on the documentation, may be give a try if you get any object using the below const pathbrowser = new Coral.PathBrowser(); Documenation : https://developer.adobe.com/experience-manager/reference-materials/6-5/coral-ui/coralui3/components.html 

@kirang29990284  did you check your role/permission if you have specifically role of Product Profile admins- allows you to add users

@JessieYu1  adding to @Jennifer_Dungan  comment refer below link https://experienceleague.adobe.com/en/docs/analytics/components/marketing-channels/mchannel-best-practices  @Jennifer_Dungan  my understanding is @JessieYu1 is looking for solution as below you mentioned if you really want to ensure yo...

@kirang29990284 @kirang29990284  issue not related to below email, but with permission and access control you have for Adobe Analytics account, check with Admin or get required access for adding new user to Adobe Analytics instance or product profile , specifically role of Product Profile adminsemai...

@aent22  may be not what you looking for  but below is possible where when you change time for range it auto adjust  

@Harveer_SinghGi1, I am not aware of any repo or documentation. The idea behind standard fields is to standardize common use cases for quick and seamless implementation with the Adobe Ecosystem for better performance. However, you can use your fields—maybe you can think of buying a car with a predef...

@robinl39529461 configure pushed audience in your target activity and define targeting based on the attribute you passed in the audience via CDP export 

@MAdhuS1  adding to the list to confirm you are using WebSDK data streaming for the dataset/schema in question, if not considering using WebSDK for Edge

@Michael_Soprano Adobe suggests using simple XDM and limiting nesting in terms of object, specifically if felid is going to be part of Primary/Secondary identity - should not done, rather simplify ERD/XDM to get required felid. If you still need to do think of scalability in terms of future requirem...