When setting up an JSON-LD Email Markup for an Event Reservation, the Location of type "Place" is required.
Is it possible to specify a VirtualLocation type for a Google Meet or Zoom session?
https://schema.org/VirtualLocation
When I test my schema using VirtualLocation, I get the error:
VirtualLocation is not a valid target type for the location property.
The type VirtualLocation is not a valid type.
You haven't mentionned the tool you're using to test, but I guess it's the Markup tester from Google ?
https://www.google.com/webmasters/markup-tester/u/0/
I feel the tool is maybe bugged ?
Because when I try with this tool
https://search.google.com/test/rich-results
It works fine
Related
Is it possible in SAP PI parameterized mapping to get the value from a field in graphical message mapping and send that value in Java Mapping?
I have a scenario where I am getting the email list from S/4HANA system in graphical mapping but I want to use that email value in the Java Mapping which is another mapping in this scenario. I tried parameter binding but neither the import or export type of parameter is useful in this scenario since none of them can store value.
Kindly let me know if it is possible to achieve or is there any other way to get it in SAP PI system.
Not sure if parameters would be your best bet here. They are mainly intended to insert some values on configuration time into mapping at runtime.
You may want to have a look at "using global variables" like here https://blogs.sap.com/2014/10/17/how-to-use-global-variable-in-sap-pi-mapping/
One solution portrayed there is to use the "Edit Java Sections" function within graphical message mapping.
Please beware that I haven't actually tried this, so YMMV
I am using the lua-geoip library.
How do I use "geoip asnum" and "geoip org" to get the asnum and org value from ipaddress using lua script?
If I understand correctly your question, you're looking to get an Autonomous System Number and ISP Organization for an IP address.
These values are stored in two databases: GeoIPASNum.dat and GeoIPOrg.dat. (Note that ASN number already contains an organization name, which may be sufficient for your purposes, for example: "AS15169 Google Inc.".)
At this moment the lua-geoip (v0.1.2) does not support either of these files.
You may add this support by cloning the country db, replacing country with asnum in the text.
https://github.com/agladysh/lua-geoip/blob/master/src/country.c
Then change query functions to use GeoIP_org_by_name instead of GeoIP_id_by_name — and push the result as a string, not country_info.
The process should be similar for the org DB should you need it.
See usage here:
https://github.com/maxmind/geoip-api-c/blob/master/test/test-geoip-asnum.c
https://github.com/maxmind/geoip-api-c/blob/master/test/test-geoip-org.c
(Full disclosure: I'm the maintainer of lua-geoip)
I need to get all issues by version id. My query is like:
http://archwork:2990/jira/rest/api/2/search\?jql\=project\=GP+and+fixVersion\=10001
working fine, but I want to get issues by VERSION
Link like:
http://archwork:2990/jira/rest/api/2/search\?jql\=project\=GP+and+version\=10001
returned "Field 'version' does not exist or you do not have permission to view it."
The two built-in version fields in JIRA can be accessed in JQL as fixVersion and affectedVersion. I suspect that you want the latter.
If you have another custom field (which is a version-type field) that you want to query, the error message suggests that you may not be using the correct name for it. The best way to check this is to type your JQL into JIRA's Issue Navigator manually (in the advanced search) and to take advantage of the dropdown box with field name suggestions to get the correct field name.
One way to bypass the problem of determining the correct JQL field name (which sometimes requires quoting, which gets slightly more messy if you are also URL-encoding the result) is to simply refer to a field by the custom field ID instead.
You can find the CF ID of a field by going to Admin->Issues->Custom Fields, finding the appropriate custom field, mousing over the "Configure" link, and then looking at the URL query parameter for customFieldId, and then use the syntax cf[xxxxxx] in your JQL instead of the field name, where xxxxxx is the custom field number.
We ran the Fortify scan and had some Access Control: Database issues. The code is getting the textbox value and setting it to a string variable. In this case, it's passing the value from the TextBox to the stored procedure in a database. Any ideas on how I can get around this Access Control: Database issue?
Without proper access control, the method ExecuteNonQuery() in DataBase.cs
can execute a SQL statement on line 320 that contains an attacker-controlled primary
key, thereby allowing the attacker to access unauthorized records.
Source: Tool.ascx.cs:591 System.Web.UI.WebControls.TextBox.get_Text()
rptItem.FindControl("lblClmInvalidEntry").Visible = false;
ToolDataAccess.UpdateToolData(strSDN, strSSNum, strRANC, strAdvRecDate, strAdvSubDate, strClmRecDate, strClmAuth, strClmSubDate, strAdvAuth, txtNoteEntry.Text);
Sink: DataBase.cs:278
System.Data.SqlClient.SqlParameterCollection.Add()
// Add parameters
foreach (SqlParameter parameter in parameters)
cmd.Parameters.Add(parameter);
The point of "Access Control: Database" is where it isn't being specific enough in the query and so could potentially allow a user to see information that they're not supposed to.
An easy example of this vulnerability would be a payroll database where there is a textbox that says the ID of the employee and gives their salary, this could potentially allow the user to change the ID and see the salary of other employees.
Another example where this is often intended functionality is in a website URL where the product ID is used in a parameter, meaning a user could go through every product you have on your site. But as this only allows users to see information they're supposed to be able to, it's not particularly a security issue.
For instance:
"SELECT account_balance FROM accounts WHERE account_number = " + $input_from_attacker + ";"
// even if we safely build the query above, preventing change to the query structure,
// the attacker can still send someone else's account number, and read Grandma's balance!
As this is pretty context based, it's difficult to determine statically so there are lots of examples where Fortify may catch this but it's actually intended functionality. That's not to say the tool is broken, it's just one of the limitations of static analysis and depending on what your program is supposed to be doing it may or may not be intended.
If this is intended to work like this, then I would suggest auditing it as not an issue or suppressing the issue.
If you can see that this is definitely an issue and users can see information that they shouldn't be able to, then the stored procedure needs to be more specific so that users can only see information they should be able to. However SCA will likely still pick this up in a latter scan so you would still then need to audit it as fixed and no longer an issue.
I'm developing some reports for Main Page in Dynamics Ax, however the problem i've got is connected with SSRS. Typical scenario i have report A and report B, i need to open report A when clicking on report B. Opening report itself is correct, but passing parameters is more tricky. After some research i got to the point when I want to run report A in browser using the adress
http://(server address)/Reports/Pages/Report.aspx?ItemPath=/Dynamics/Reports.VendorsOpenTransactionsCount.AutoDesign1&rs:Command=Render&VendOpenTrans_dataAreaID=dor&VendOpenTrans_p1=2011-07-21&VendOpenTrans_p2=2011-07-21
and then i get report displayed(main window) but non of the parameters are validated into proper textboxes, and changing the value of them doesn't have any impact.
can anyone here help me with that "challenge"
Actually, I believe the critical difference is whether you are passing parameters (via URL) to a report that is using database engine or the SSAS - the analytical engine as a data source.
If your data source is the analytical engine then your parameter should be given in the 'dimension format', rather than in the precise format, like &parmname=140, etc. Allow me to explain using specific example and using SSAS data source for this illustration (there is plenty of solutions available on the net for the database engine based solution, including Microsoft postings).
My server name is FRELASM.
So, I have SSAS data source called DealerSource (not visible here).
I have parameter defined in the parameter's section of the SSRS as: #DwDimDealerCorpDlrNbr
In SSAS I have the following dimension:
[Dw dim Dealer] that has attribute: [Corp Dlr Nbr] ==> giving: [Dw dim Dealer].[Corp Dlr nbr]
What I want is to show a report for a single dealer 'number' (but it is a text field, hence the leading zeros) equal to 00140. So, I am looking for Corporate dealer number=00140.
The parameter passing DOES NOT WORK if I use this [this would be find against database engine, but it does not work with SSAS).
What you need is this:
replace constant 00140 with [dimension].[attribute].[value]
do not use & character, rather replace it with: %26.
So, the working version is this.
Can you take a look at this page: http://msdn.microsoft.com/en-us/library/ms155391.aspx
It explains about when you can pass parameters via URL. Maybe your parameters are not set to Prompt for user input. HTH.