bullhorn / extension-configuration-starter Goto Github PK

Tried with several ways to upload an interaction to a seconday private Label, changed interaction name, extension name, privateLabelIds property, etc.

The interaction is always populated to the primary private label defined in the user defined in the environment json file.

The only way I was able to upload an interaction to the different private label was by changing the "Private Label:" on user profile. The deploy is not working for other private labels regardless these are correctly set on the "Additional Private Labels:" field on user profile.

Can you advise if this is an officially support approach to deploying interactions?

I believe page interactions stored on the corporation level. Is this correct? If so, would this lead to duplication when deploying interactions to multiple private labels on the same corporation?

Is there a way to upload interactions to the timeAndExpense entity that is embedded in Placement?

I couldn't find the correct way to write the field name, I tried "timeAndExpenseBranch" which is the field name, also tried the same way that is found on API.form.controls "timeAndExpense.timeAndExpenseBranch"; but I face error "No Field Map found for timeAndExpenseBranch"

Also tried changin the entity name in extension.json; used "Placement1.timeAndExpense", "timeAndExpense", "TimeAndExpense1", etc. Receiving error "Invalid Extension: Invalid Entity: Placement1.timeAndExpense".

extension.json

{
    "name": "amp-interactions",
    "fieldInteractions": {
        "Placement1": [
            "./dist/field-interactions/placement/**"
        ]
    }
}

time-and-expense-branch.ts

const interaction: FieldInteraction = {
    fieldName: 'timeAndExpenseBranch',
    event: 'change',
    invokeOnInit: false,
    name: '1218Global',
    sortOrder: 10,
    enabled: true,
    script: (API: FieldInteractionAPI) => {

        console.log('hello');

    },
};

export default interaction;

Does this extension-configuration-starter support deploying interactions to custom objects? If so how should the extension.json file be configured to include custom objects? Thanks!

Seems when I run the task to deploy code it does a complete replace each time and adds a new ID to the page or field interaction even on exiting scripts im tweaking slightly. Is there a way to configure this repository to look for existing scripts and update instead of do a full replace with a net new interaction ID.

EX: pushed the logger.ts script within the client-corporation\name\logger.ts which deployed no problem and had a field interaction ID of 11 then tweaked the language in the console.log, deployed again and the field interaction had an ID of 13. I didnt change the path name of the src file, the only property I changed within the script was 'enabled' from true to false as well as the previously mentioned tweak to the language in the console.log (see below)

Would be nice for this repository to recognize that the core of the script hasnt changed, just the contents inside therefore do an update to the existing instead deleting and adding net new in order to keep the same ID.

Let me know if im missing anything here. Thanks!

When I upload a single interaction to 2 private labels, only the 1st private label is updated; when BH cli tries to upload to the 2nd private label, a duplicate error is faced:

{ detailMessage: "Found duplicate extension of type 'FieldInteraction'. It was not installed.", dupeFields: { fieldMapID: 5984, name: '1218 - Set Workday Company' }, severity: 'WARNING', type: 'DUPLICATE_EXTENSION_POINT_PERSISTENCE_MESSAGE' }

I tried inserting an env variable in the interaction name, but this only works inside the script, not the name of the interaction:
name: '1218 - ${labelName} - Set Workday Company',

Also tried defining the private label ids in the interaction properties but same error:
privateLabelIds: ["38303","38305"],

Attached is the log of the "npm run deploy"
log.txt