Campaign Adobe IO Rest API - Not able to set Organizational Unit & Geo Unit | Community
Skip to main content
Premkarthic-7WP
Premkarthic-7WP
New Participant
August 29, 2017
Solved

Campaign Adobe IO Rest API - Not able to set Organizational Unit & Geo Unit

  • August 29, 2017
  • 15 replies
  • 12215 views

Hi,

We are using Adobe IO Rest API to create a profile and add the subscriptions to the profile.

We are always getting the error "orgUnit property is not valid for the 'profile' resource." when we trying to override the default value ("all") set by profileAndServicesExt/profile api. Same applicable for geoUnit.

Note: We are using custom profile that get extended from default one with

Any pointer to fix this will help us more.

-Prem

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by vraghav

Hi Kornel,

I did verify from Engineering. They had released the feature to have Geo and Org units assigned based on the settings of security group used in Integration on Adobe.IO but the feature was removed as it lead to an issue which was too risky to fetch.

Now they are working on providing you with the ability to push geo and org unit on the API payload itself.

At the moment, you can have profiles created from API and then have a workflow running on the instance which updates profiles every 5 minutes with correct geo and org unit.

Regards,
Vipul

15 replies

Show previous replies
florentlb
florentlb
New Participant
October 11, 2017

Hi Kornel,

I will check if there are plans with the team. If you have the same issue, please do as Vipul suggested and raise a request to support so that our engineers have a look at it.

Thanks,

Florent

Kornel_Keseru
Kornel_Keseru
New Participant
October 6, 2017

Hi,

I ran into the same issue on Adobe Campaign Standard. Our profile resource was extended with access authorization fields. We create profiles via the REST API and need to put the new profiles into the right Org and Geo units.

We have a lot of geo units to support (>60) and it would be too complicated generating so much api clients and switching between them when issuing the REST API calls.

Is there any other solution?

Is this feature expected to appear in a new release in the near future?

Thanks,

Kornel

vraghav
vraghav
Employee
September 24, 2017

Hi Prem,

I've redid my test for step1 as done in past but it is not working anymore.

Can you please log a case with support to report this to Engineering.

Regards
Vipul

Premkarthic-7WP
Premkarthic-7WPAuthor
New Participant
September 6, 2017

Hi Vipul,

We have tried the first approach as you said, but we are always seeing the profile has been created with value of orgUnit and GeoUnit pointing to the value "all" instead of the one that we chosen on security group.

Steps Followed,

  1. Created custom security group with OrgUnit and GeoUnit pointing to our custom value on campaign server.
  2. Created mapping for that security group on adobe marketing cloud with the format "Campaign Standard - <Tenant ID> - <Security group>".
  3. Created Adobe IO integration for campaign with value pointed to the custom security group.
  4. Made Post call to the profileandservicesext api.

Any Pointer to fix this will help us more.

Thanks,

-Prem

    vraghav
    vraghav
    Employee
    August 29, 2017

    Hi Prem,

    At the moment, ACS doesn't allow you to pass orgUnit and geoUnit in the payload. This is a feature which is part of the proposed enhancements of ACS.

    At the moment, you need to have security groups defined per geoUnit + OrgUnit combination.

    Then for these security groups, create an individual integration point in Adobe IO.

    Use that specific integration to add profiles into ACS, they will get the designated geo and org unit details.

    If this is cumbersome for you, the only other option is to have a workflow that runs every x minutes to update the profiles based on country or specific custom field that can help determine the relevant geo and org units.

    Hope this helps.

    Regards,
    Vipul

    Terms & ConditionsAccessibility statement

    Loading footer...