1 of 1 people found this helpful
any more details in the logs of Supplier Portal or Product 360?
Did you try login into the Web UI directly with the service user as well?
Thank you for a quick reply! This problem has now somehow disappeared, may have been just some glitch.
However, if you happen to know this, I have another problem related to the article detail tab. I have now modified the article.detailtab.xml in webdefinitions. This change (an additional field on the first tab) shows up in Web Access, but for some reason not in Supplier Portal. What could be the problem?
did you login with the service user directly into the Web UI and check if this would make the field visible or not?
All common visibility and access rights should come from the setup of that user and this would be the first thing to check I assume.
When I log on with the SP service user to Web Access, I only see empty table view and detail view and nothing else. I suppose there is something I need to adjust in those rights to get it right. I've followed the installation instructions when setting up that user in PIM, but I guess that's not the whole story.
However, I've found the setting that fixed my initial problem. The field that I created in SP, was an attribute, so I needed to give SP Item Editor group the right "item attribute values, general access". I guess it was not in this list of rights listed in the installation document or I missed it somehow. Now this works in SP.
I am having this issue as well and have checked everything on the webfronted.properties as well as the permissions in pim. Is there a specific action right that needs to be selected? I am able to access in QA but not PROD.
what kind of issue do you have. If you open the Item Editor is there nothing or is he not loading the page.
If so please keep in mind that the Item Editor will open the P360 WEB as an X Frame which is by default not active.
See webfrontend.properties -> web.client.xframeoptions=
Thanks for you response. In our process of upgrading the QA information was put in the PROD webfronted.properties so once I updated that and restarted my servers this began working.