Thanks @hamalk, for the clarification. In my opinion this is something R&D should have placed some sort of validation somewhere. Hope you can raise this as a concern to the relevant teams.RegardsKelum
Hello Harshini, @hamalk Hope you can advise on this. Let’s assume a core component ‘X’ is currently false in the customer’s (Cust Repo and Base repo) SolutuionSet.yaml file. My understanding is that ‘X’ is unlicenced to this customer. But still, the customer can amend the SolutuionSet.yaml, make ‘X’ as True, then successfully create a delivery and deploy it in the Use place without any issues. It doesn’t sound right. Where did that cross-check happen? Is it only when applying the next RU ? Could you please share some insight?ThanksKelum
@Mathias Dahl - Manged to get this working in a Partner Enablement Environment. Thanks for your help. 🍻
Thanks @Mathias Dahl - Will give it a go. Cheers
That’s great @Link. So, is it just a matter of associating DOCUMENT_ATTACHMENT PS with your PSs? Isn’t it?
Then it could be a permission issue. The below image is from a IFS Cloud env. As I remember it’s called DOCUMENT_ATTACHMENT in APPS10. Give it a go by granting that Permission set to the user.
It due to missing data in above page. You may add all file extensions you are working with.
Hi @chanaka-shanil,May I get your advice on the matter, please. Your support is much appreciated.Thanks
Agree. I’ll wait for @chanaka-shanil thoughts from the IFS Cloud File Storage side before returning to the customerThanks again, @Mathias Dahl.Cheers
Thanks @Mathias Dahl, They are mainly looking for a cheaper alternative due to the rapid growth of the DB due to documents. As they already have a separate Azure subscription, the idea is to utilize that. Maybe there is no price difference from azure perspective. Still, they would like to explore all possible options before deciding.Thanks for directing to @chanaka-shanil Cheers !
Hi @Mathias Dahl, As always, thanks for sharing and providing valuable clarifications. I may add just one more related question connected to one of our customers.They are on 23R2 and planning to move to 24R1 before going LIVE later in the year. It’s a Cloud Deployment and currently uses the default Database as the File Storage option. They won’t move from Database to File Storage. As indicated in the documentation (Index - Technical Documentation For IFS Cloud), the File Storage uses an Azure Blob Storage Account to store files in the Cloud deployment model. Is it possible to have a completely different Azure subscription for this Azure Blob Storage?ThanksKelum Ferdinandez
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
