Doc Connection from Project Demand Line to Purchase Req Line - anyone done the mechanics?

Hello ​@Mathias Dahl

I hope you’re doing well.  I’ve got my setup complete, the help documentation was mostly helpful, thank you.  I have a question or two on the functionality of the Editable field.  It does not seem to matter if it’s set to None or Target (I didn’t test with Source).  I’ve made a little write-up of my setup and testing results and it is attached.  It’s quite possible I tested incorrectly but…..

I’ll document the full setup in a little bit, that way if I forget how to do it, I’ll be able to refer to this spot.🙂

If you can offer any help with the Edible field, I’m all ears.
Patrick

​@PIreland 

I think the documentation is quite clear about the Editable field:

Lifting out the part about None:

• None (default) - This indicates that the attachment panel is in a read-only mode for the specified service and target. No objects can be attached or removed on the target business object.

Does that not describe what you see?

​@Mathias Dahl 

From the field level help:

This controls if the inherited object connection is read only or not. It also controls which LU any new connections will be registered for. This can have three different settings:

• None (default) - This indicates that the inherited object connection is read only and no new connections can be made.

My target is PurchaseReqLinePart and I cannot detach the document that was inherited.  Okay.

But the help goes on to say “…attachment panel is read only….” no objects can be attached to the target business object. I can attach any number of objects to the target using Attach Existing or New Document. If “no objects can be attached or removed on the target business object”, how come I can?

I hope this gives more detail about what it is I’m seeing.

Patrick

​@PIreland 

Thanks, Patrick. That makes it clearer 🙂 Well, it should have worked like the documentation describes, that you can make Attachments / Documents "locked", for certain LUs. If that doesn't happen I can understand the confusion.

​@PIreland 

I tried this experimental OCT rule:

And I get this error when I try to create and connect a new document (in the Document Folder screen):

This is in 25R1, to be released in a few month’s time.

At first, I didn't get any error, and that was because my rule was not set to Active, so please check that.

Also tried with this slightly less strange rule:

Same result: I can neither create a new document and connect it, nor attach an existing one.

Mathias Dahl wrote:

Also tried with this slightly less strange rule:

Same result: I can neither create a new document and connect it, nor attach an existing one.

​@Mathias Dahl at the Source LU or Target LU?

I just tried with Project Demand as the source and Purchase Requisition line as the Target and I don’t get the results you two are getting.  I haven’t worked with DocFolder as the target.  

matt.watters wrote:

Mathias Dahl wrote:

Also tried with this slightly less strange rule:

Same result: I can neither create a new document and connect it, nor attach an existing one.

​@Mathias Dahl at the Source LU or Target LU?

Target, of course 🙂 The page the user is on has the target LU/entity.

Perhaps the target LU is not what you think it is? 🤔 

Well, I go to the target LU and see the object connection and that’s how I think that I’m on the LU that I think it is.  (Purchaser Order Line of the Purchase Order.)

Here is a detailed example in the https://ifsgcc1-d06.demo.ifs.cloud/main/ifsapplications/web/start database.  I think we all have access to it.  The example I have below is as simple as it gets, I would say.

My OCT:
 

The connection is transformed, OK

On the target LU, I cannot detach the document, OK.

But, I can add a document:

Clearly, I’m not getting the same result as you both.  What am I missing?

Patrick

​@Mathias Dahl 

How did you build the transformation from SalesPart to DocFolder?  The keys on sales part are PN and Site but I’m not seeing how you get the document to go to the folder.

/Patrick

I modified the key mapping in the Transformation Method field to hard code the values for the source keys, just for testing the rule.

​@PIreland 

I cannot log in to the environment you linked to and we probably should not even paste links like that here, even if you didn't provide any credentials.

That being said, I replicated your rule there and I get the same result as I did earlier. I cannot create and attach a new document to the inventory part. Again, using 25R1, which you don't have access to.

By the way, did you modify that rule you showed? I didn't find any system-defined rule with those two LUs...
 

​@PIreland to clarify, I am seeing the same behavior as you in my 24.2.3 world with the setting of None. I can create new documents, attach existing, and detach non-transformed documents at the Target.

That’s good to hear, ​@matt.watters .  At least I know I’m not crazy.  The million dollar question is what’s changed?  

Thank you.

Patrick

​@Mathias Dahl 

In response to the question ‘By the way, did you modify that rule you showed? I didn't find any system-defined rule with those two LUs…’  I created that rule by duplicating the existing one for MediaLibrary.  When it is duplicated, the System Defined and Active sliders remain TRUE.  .  When I create the transformation from scratch, both of those remain FALSE.

/Patrick

I’m not sure what’s wrong in your environments.

I just tested in 24R2 as well. I have these rules for InventoryPart:

I changed Editable to None in that first rule there and I went from being able to create a new document to not be able to do it, in the Inventory Part screen.

Magic fingers? :-)

I don’t know that I have magic fingers.  Would have DocMan Admin privilege have any effect on this?

I’ll keep chipping away, I’ll get to the bottom of it eventually, I hope. 

​@matt.watters, ​@Mathias Dahl 
I think I figured it out.  If you have two sources for a target and the OCT editable field is set to Target, the target LU will follow the functionality of the Target attribute regardless of the None setting.

That’s it!
Patrick