Skip to main content

Hello!

We are working on some integration with Boomi and have run into a roadblock with a custom integration projection. We were under the impression that when you add two Entities to a custom projection that it would combine the data from those two entities into a single API. 

We need to pull the full address and the address type, unfortunately that information is in two different places. 

Here’s our Custom Projections - the Categories has disappeared, it was Integration, not sure why it’s not showing. 

We have out two entities, CustomerInfoAddress, CustomerInfoAddressType and we’ve done our Associations and Key Mappings. 

 It’s published and when we go to API Explorer and look at the API Doc, we have API’s for each entitiy but not them combined. 

Neither one of these have all the information we need. Are we misunderstanding how the custom projections work or is there something wrong with how the API’s are being generated. I did a case to IFS asking this exact question and they told me to contact Boomi. That doesn’t help because my question is related to how the Custom Projection creates the API’s. 

hello @SaraCrank ,

from the screenshot, it seems that you use IFS cloud. If yes, there is a projection

CustomerSalesInfoService

 

and it has a function GetCustomers which has required info.

 

regards,

Kajetan


Hi Sara!

We are deep in the weeds of installing a shipping software via API calls and I came across this post. We too have found that addresses, along with part information required, come from many different places in IFS. We’ve attempted to minimize this by adding custom fields to the shipment screen, but it’s getting excessive to say the least. Our next stop was to pull back and create a custom page/projection. This research led me to your post.

Can you share some details of why you went down this custom page/projection and if it resulted in success for your business?

Any knowledge shared would be greatly appreciated!!

Thanks,

Jeff

 


Reply