Skip to main content

 Some users are receiving an error message “The File Type is not available” when trying to use a certain file type in External File Assistant. 

I have confirmed that changing to a different permission set resolves this issue, but I have not been able to pinpoint what needs to be granted in the orignial permission set.

How can I determine what projection or other grant needs to be added to the permission set to resolve the issue? 

I have tried using the debugger but the projection listed (ExternalFileAssistantHandling) is not the issue.

 



 

11:36:49 INFO - REQUEST method "GET"
11:36:49 INFO - REQUEST uri "https://abc.def.com:12345/main/ifsapplications/projection/v1/ExternalFileAssistantHandling.svc/GetDefaultFileTypeInfo(Company='DHP',FileType='ExtPosPayCheck',ProcessOption=IfsApp.ExternalFileAssistantHandling.ProcessOptionsEnum'Online')?odata-debug=json"
11:36:49 INFO - REQUEST protocol "HTTP/1.1"
11:36:49 INFO - REQUEST headers {"Host":"abc.def.com:12345","sec-ch-ua":"\"Not_A Brand\";v=\"8\", \"Chromium\";v=\"120\", \"Microsoft Edge\";v=\"120\"","Accept":"application/json;odata.metadata=full;IEEE754Compatible=true","X-Requested-With":"XMLHttpRequest","Accept-Language":"en-US,en;q=0.5","sec-ch-ua-mobile":"?0","User-Agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 Edg/120.0.0.0","sec-ch-ua-platform":"\"Windows\"","Sec-Fetch-Site":"same-origin","Sec-Fetch-Mode":"cors","Sec-Fetch-Dest":"empty","Referer":"https://abc.def.com:12345/main/ifsapplications/web/assistant/ExternalFileAssistant/Assistant;path=0.2026593824.1876323749.2098603466","Accept-Encoding":"gzip, deflate, br","Cookie":"XSRF-TOKEN=M5UP-MXQX-WJCB-C6E5-8KDZ-IM51-Y8Q5-XCGF; JSESSIONID=vJTeSE5Ie1G9QQNcJY-tLJKus8-_W6QOjzHpqyHQfNl7VmnMuqzE!-1182627715; _WL_AUTHCOOKIE_JSESSIONID=CXcu1hwkJSnkvg9Cd9nq","ECID-Context":"1.00jQFBTH04LFw0zzjr0Afz4cndy3zNIz90003F80008Ug;kXjE","Connection":"Keep-Alive","X-Forwarded-For":"10.10.48.155","X-WebLogic-KeepAliveSecs":"30","X-WebLogic-Request-ClusterInfo":"true","x-weblogic-cluster-hash":"wzCbc8umKb0cV2bauve9kqrjGm4"}
11:36:49 INFO - RESPONSE status {"code":"500","info":"Internal Server Error"}
11:36:49 INFO - RESPONSE headers {"OData-Version":"4.0","Content-Type":"application/json"}
11:36:49 INFO - RESPONSE body "{\"error\":{\"code\":\"DATABASE_ERROR\",\"message\":\"Database error occurred. Contact administrator.\",\"details\":e{\"code\":20105,\"message\":\"ORA-20105: ExternalFileAssistantHandling.INVFILETYPE: The File Type is not available\"}]}}"
11:36:49 ERROR - INVFILETYPE - (Server Application Error): The File Type is not available Database error occurred. Contact administrator. undefined
11:36:49 ERROR - Command error: (INVFILETYPE) - The File Type is not available, details: "e{\"code\":20105,\"message\":\"ORA-20105: ExternalFileAssistantHandling.INVFILETYPE: The File Type is not available\"}]" undefined
11:36:49 DEBUG - CMD(1): Error: The File Type is not available

 

Hi @hreavis,

Please try granting ExternalFileAssistantHandling projection as per the error message. If the projection is already granted, then check if there is a difference in the access levels between the permission sets(Custom/Full etc.). 

Hope this helps!

@Charith Epitawatta ExternalFileAssistantHandling is already fully granted - every entity action is granted and there are no Projection Action Grants for that projection.

Do you have any other suggestions?

Thanks!

 

Is there an update on this error? 

We get one step further in the process but have the same error. Permissions for ExternalFileAssistant are fully granted.

 

 

@SAXBBSOT We are still experiencing this issue.

We found the cause for our error “File Type XXX is not available for the user”.

In our case it was not a permission error. In IFS cloud it’s not possible to crerate new external file Types. See for details: https://community.ifs.com/finance-financials-42/create-a-new-external-file-type-30279?tid=30279&fid=42

The error is only triggered when we use file types we created in APPS 10. System defined file types are working. This means we have to adjust our workflow by using the default file types but separate with file Template per company instead of a file type per company.

The topic is also already on the idea wall: 

 

Reply


Terms & ConditionsCookie settings