Client Context JSONP Properties not in Generic Store Property, can it be manual? | Community
Skip to main content
ehsanketa
ehsanketa
October 16, 2015
Solved

Client Context JSONP Properties not in Generic Store Property, can it be manual?

  • October 16, 2015
  • 1 reply
  • 542 views

Not sure if it's a installation issue or a missing step with Client Context, JSONP Store and Generic Store Component in Segments.

After dragging a new JSONP store into Client Context,

Setting up a JSONP url and doing a Fetch it downloads all the properties into the store.

When loading up a new segment and using the Generic Store Component, to use the data in JSONP store, the Property drop-down section does NOT load the properties that were ORIGINALLY FETCHED in the previous step. (see screenshot red box, drop-down is null). 

1) Why would this happen?

2) Can we type the property name in manually and assume it works?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sham_HC
  1. This could happen if clientcontext is not registered (May be some other thread is unregistering)
  2. You can type & proceed it will work in personalization as long it is registered and valid property.  But I would investigate what is causing the issue to resolve rather than assuming.  

Get a official suppoer help if you need to debug more. 

1 reply

Sham_HC
Sham_HCAccepted solution
Level 10
October 16, 2015
  1. This could happen if clientcontext is not registered (May be some other thread is unregistering)
  2. You can type & proceed it will work in personalization as long it is registered and valid property.  But I would investigate what is causing the issue to resolve rather than assuming.  

Get a official suppoer help if you need to debug more. 

Terms & ConditionsAccessibility statement

Loading footer...