Hi

I know I’m not actually answering your direct question, but is it worth thinking about why the ReceiptInvLocation entity needs to be editable?  Is there a particular field that you are looking to update?

By the time this information is being shown to the user, the items have been receipted, probably for inspection, and are already considered to be in stock.  If the location needs to be changed then the user process is to use the relocate option.

There could be potentially other data which would need to be updated if the ReceiptInvLocation entity could just be edited directly (such as inventory parts in stock, if the location is changed) which is why it’s not already enabled in IFS

MMck

Thank you for the response. ​@MMcK  I have a migration from IFS 8 to cloud version, and in IFS 8 there was a customized field 'No. of Labels' that could be edited, which then summed the values from each row to 'Total No. of Labels'. In IFS 8, RECEIPT_INVENTORY_LOCATION could be edited, but in the cloud version, RECEIPT_INV_LOCATION can no longer be edited.

I’m sorry, I don’t know why it would have changed between IFS 8 and Cloud, I’m only familiar with the Cloud version.

I guess a get-round would be to implement an action which specifically updates your custom field, but perhaps someone else may be able to assist with why the capability has been changed in Cloud.

Hello.

Possibly due to missing lu dependency. The place where your error is being raised it should say:

 Error_sys.Odp_Record_not_exists(ReceiptInvLocation.lu_name); which is why its raising the error.

Take a look at other entities being used in the projection file for how they include lu dependencies and try adding the receiptInvLocation lu dependency in that way. 

Fore example, here is how the receiptInfo lu dependency is added for the ReceiptInfo entity

Thanks,

LEdwards​

Hi, ​@Edwards 

Thank you for the response. I tried following your suggestions but it still gives the same error.

I found a way to solve the problem by adding the API name in the exec because the core file didn't include the API name. Thank you everyone for your help.
 

Nice job . Good to know that for the future