added 117 characters in body
Source Link
  1. You need to use fh:user:date as the claim uri.
  2. You also need with Tridion 2013 to enable claim forwarding for that claim. You can do this in the cd_ambient_conf.xml by adding <Claim Uri="fh:user:date"/> within the GloballyAcceptedClaims element.

However, this is not enough, because the date format generated by the FootprintDate control is not recognized by Fredhopper, probably because of how. Here is the time ends up encodedresult in the FH query: &fh_user_date=2013-12-08T00%3A00%3A00

Using a custom ASP.Net User Control I am able to set this claim and get a promotion triggered correctly. You can actually check the fh_user_date URL parameter value as part of the FH Query in the cd_core_log file, when logging is set in DEBUG mode. A fh query appears as follow in the log:

DEBUG Query - Executing query: fh_location=

So you can either search for "fh_location" or "fh_user_date" directly to find the claim value that you are working with. For instance fh_user_date=20131207 works.

I looked at the Fredhopper Learning Center (login required) and the format of the fh_user_date parameter is simply YYYYMMDD.

To get to the bottom of this, we may need to investigate a bit more to figure out first what date format are accepted as URL parameters by Fredhopper, then create a custom Footprint date control which would output that format, or modify the existing FootprintDate control if that is acceptable.

  1. You need to use fh:user:date as the claim uri.
  2. You also need with Tridion 2013 to enable claim forwarding for that claim. You can do this in the cd_ambient_conf.xml by adding <Claim Uri="fh:user:date"/> within the GloballyAcceptedClaims element.

However, this is not enough, because the date format generated by the FootprintDate control is not recognized by Fredhopper, probably because of how the time ends up encoded in the FH query: &fh_user_date=2013-12-08T00%3A00%3A00

Using a custom ASP.Net User Control I am able to set this claim and get a promotion triggered correctly. You can actually check the fh_user_date URL parameter value as part of the FH Query in the cd_core_log file, when logging is set in DEBUG mode. A fh query appears as follow in the log:

DEBUG Query - Executing query: fh_location=

So you can either search for "fh_location" or "fh_user_date" directly to find the claim value that you are working with. For instance fh_user_date=20131207 works.

To get to the bottom of this, we need to investigate a bit more to figure out first what date format are accepted as URL parameters by Fredhopper, then create a custom Footprint date control which would output that format, or modify the existing FootprintDate control if that is acceptable.

  1. You need to use fh:user:date as the claim uri.
  2. You also need with Tridion 2013 to enable claim forwarding for that claim. You can do this in the cd_ambient_conf.xml by adding <Claim Uri="fh:user:date"/> within the GloballyAcceptedClaims element.

However, this is not enough, because the date format generated by the FootprintDate control is not recognized by Fredhopper. Here is the result in the FH query: &fh_user_date=2013-12-08T00%3A00%3A00

Using a custom ASP.Net User Control I am able to set this claim and get a promotion triggered correctly. You can actually check the fh_user_date URL parameter value as part of the FH Query in the cd_core_log file, when logging is set in DEBUG mode. A fh query appears as follow in the log:

DEBUG Query - Executing query: fh_location=

So you can either search for "fh_location" or "fh_user_date" directly to find the claim value that you are working with. For instance fh_user_date=20131207 works.

I looked at the Fredhopper Learning Center (login required) and the format of the fh_user_date parameter is simply YYYYMMDD.

To get to the bottom of this, we may need to create a custom Footprint date control which would output that format, or modify the existing FootprintDate control if that is acceptable.

added 494 characters in body
Source Link
  1. You need to use fh:user:date as the claim uri.
  2. You also need with Tridion 2013 to enable claim forwarding for that claim. You can do this in the cd_ambient_conf.xml by adding <Claim Uri="fh:user:date"/> within the GloballyAcceptedClaims element.

However, this is not enough, because the date format generated by the FootprintDate control is not recognized by Fredhopper, probably because of how the time ends up encoded in the FH query: &fh_user_date=2013-12-08T00%3A00%3A00

Using a custom ASP.Net User Control I am able to set this claim and get a promotion triggered correctly. You can actually check the fh_user_date URL parameter value as part of the FH Query in the cd_core_log file, when logging is set in DEBUG mode. A fh query appears as follow in the log:

DEBUG Query - Executing query: fh_location=

So you can either search for "fh_location" or "fh_user_date" directly to find the claim value that you are working with. For instance fh_user_date=20131207 works.

To get to the bottom of this, we need to investigate a bit more to figure out first what date format are accepted as URL parameters by Fredhopper, then create a custom Footprint date control which would output that format, or modify the existing FootprintDate control if that is acceptable.

  1. You need to use fh:user:date as the claim uri.
  2. You also need with Tridion 2013 to enable claim forwarding for that claim. You can do this in the cd_ambient_conf.xml by adding <Claim Uri="fh:user:date"/> within the GloballyAcceptedClaims element.

However, this is not enough, because the date format generated by the FootprintDate control is not recognized by Fredhopper, probably because of how the time ends up encoded in the FH query: &fh_user_date=2013-12-08T00%3A00%3A00

So we need to investigate a bit more to figure out first what date format are accepted as URL parameters by Fredhopper, then create a custom Footprint date control which would output that format, or modify the existing FootprintDate control if that is acceptable.

  1. You need to use fh:user:date as the claim uri.
  2. You also need with Tridion 2013 to enable claim forwarding for that claim. You can do this in the cd_ambient_conf.xml by adding <Claim Uri="fh:user:date"/> within the GloballyAcceptedClaims element.

However, this is not enough, because the date format generated by the FootprintDate control is not recognized by Fredhopper, probably because of how the time ends up encoded in the FH query: &fh_user_date=2013-12-08T00%3A00%3A00

Using a custom ASP.Net User Control I am able to set this claim and get a promotion triggered correctly. You can actually check the fh_user_date URL parameter value as part of the FH Query in the cd_core_log file, when logging is set in DEBUG mode. A fh query appears as follow in the log:

DEBUG Query - Executing query: fh_location=

So you can either search for "fh_location" or "fh_user_date" directly to find the claim value that you are working with. For instance fh_user_date=20131207 works.

To get to the bottom of this, we need to investigate a bit more to figure out first what date format are accepted as URL parameters by Fredhopper, then create a custom Footprint date control which would output that format, or modify the existing FootprintDate control if that is acceptable.

unable to add xml in a code block
Source Link
  1. You need to use fh:user:date as the claim uri.

    You need to use fh:user:date as the claim uri.
  2. You also need with Tridion 2013 to enable claim forwarding for that claim. You can do this in the cd_ambient_conf.xml as follows:

    You also need with Tridion 2013 to enable claim forwarding for that claim. You can do this in the cd_ambient_conf.xml by adding <Claim Uri="fh:user:date"/> within the GloballyAcceptedClaims element.

However, this is not enough, because the date format generated by the FootprintDate control is not recognized by Fredhopper, probably because of how the time ends up encoded in the FH query: &fh_user_date=2013-12-08T00%3A00%3A00

However, this is not enough, because the date format generated by the FootprintDate control is not recognized by Fredhopper, probably because of how the time ends up encoded in the FH query: &fh_user_date=2013-12-08T00%3A00%3A00

So we need to investigate a bit more to figure out first what date format are accepted as URL parameters by Fredhopper, then create a custom Footprint date control which would output that format, or modify the existing FootprintDate control if that is acceptable.

  1. You need to use fh:user:date as the claim uri.

  2. You also need with Tridion 2013 to enable claim forwarding for that claim. You can do this in the cd_ambient_conf.xml as follows:

However, this is not enough, because the date format generated by the FootprintDate control is not recognized by Fredhopper, probably because of how the time ends up encoded in the FH query: &fh_user_date=2013-12-08T00%3A00%3A00

So we need to investigate a bit more to figure out first what date format are accepted as URL parameters by Fredhopper, then create a custom Footprint date control which would output that format, or modify the existing FootprintDate control if that is acceptable.

  1. You need to use fh:user:date as the claim uri.
  2. You also need with Tridion 2013 to enable claim forwarding for that claim. You can do this in the cd_ambient_conf.xml by adding <Claim Uri="fh:user:date"/> within the GloballyAcceptedClaims element.

However, this is not enough, because the date format generated by the FootprintDate control is not recognized by Fredhopper, probably because of how the time ends up encoded in the FH query: &fh_user_date=2013-12-08T00%3A00%3A00

So we need to investigate a bit more to figure out first what date format are accepted as URL parameters by Fredhopper, then create a custom Footprint date control which would output that format, or modify the existing FootprintDate control if that is acceptable.

added 2 characters in body
Source Link
Loading
Source Link
Loading