I have a requirement to fulfill where i have to fetch data from the data source.. In that the number of pages in a report might vary due to the number of times the customer has purchased. Basically Customer Number is the primary Key and based on the Customer Number the report will run and each invoice will be in a different page. The template of invoice will be same except for few values. It is in pdf format..
My question is how can i create a report in such a way it takes the default template and creates many invoices based on the number of invoices present .....
Go to Page Explorer and add a Page Set.
Set Query property for your page set
Put your page inside set
Set proper Grouping and Sorting property for your page set.
Related
I would like to create a Saved Search where it gets the Budget data from the Budget page but at the item level rather than the summary level (see screenshots):
Is this possible where I can start from New Saved Search and get 12 records per account or can I only get the Saved Search at the top level with what was totaled for that account group?
I tried creating a Saved Search based on the Budget Page and that only got me on the summary level. I looked online on Orcale's documentation, and there does not seem like there is a way without coding? I would like to avoid that if feasible. I do not mind adding columns to the results tab or filtering on a proper criteria if I am just doing that part wrong.
I have a calculated column in SharePoint On-Premises that shows the number of days till a due date which works perfectly for a day or so then stops calculating, but if I go to the list settings and click the column and click ok then it calculates again?
Has anyone experienced an issue similar to this. I had this issue in both 2013 but within a few weeks moved to 2016 and still the same issue.
I've tried " " blank and also "" empty so not sure if that is causing the issue??
Is it a problem with the formula?
Here is the formula:
=IF(ISBLANK([Due Date])," ",
IF(ISERROR(DATEDIF(NOW(),[Due Date],"d"))," ",DATEDIF(NOW(),[Due Date],"d")))
Calculated columns cannot contain volatile functions, which includes those that depend on the current date.
The values in SharePoint columns--even in calculated columns--are stored in SharePoint's underlying SQL Server database.
The calculations in calculated columns are not performed upon page load; rather, they are recalculated only whenever an item is changed (in which case the formula is recalculated just for that specific item), or whenever the column formula is changed (in which case the formula is recalculated for all items).
If you need to show a dynamic value that changes with the passage of time, you have a few alternatives.
Client-Side Rendering
Consider using client-side rendering which lets you use JavaScript to dynamically determine how records in a list view are displayed. This JavaScript runs upon page load, so it can handle current time-dependent values much better than a calculated column.
To use client-side rendering, you create a JavaScript file that controls how the view displays. You upload that file to somewhere on SharePoint where people will have at least Read access to it, then edit the list view web part that you want to display differently and set its "JSLink" property to point to your JavaScript file.
Check out this answer for an example of using a JSLink file to spoof a dynamic date field.
Microsoft also provides some documentation here but I think they do more work than is necessary (creating an entire new list definition project in Visual Studio for their example instead of just creating a JSLink JavaScript file for an existing list).
Other Options
A few other options are mentioned in the older question linked above:
Conditional Formatting: You can apply conditional formatting to highlight records that meet certain criteria. This can be done using SharePoint Designer or HTML/JavaScript.
Filtered List views: Since views of lists are queried and generated in real time, you can use volatile values in list view filters. You can set up a list view web part that only shows items where Created is equal to [Today]. Since you can place multiple list view web parts on one page, you could have one section for today's items, and another web part for all the other items, giving you a visual separation.
A workflow, timer job, or scheduled task: You can use a repeating process to set the value of a normal (non-calculated) column on a daily basis. You need to be careful with this approach to ensure good performance; you wouldn't want it to query for and update every item in the list if the list has surpassed the list view threshold, for example.
To expand on the Filtered List Views option, you can have a view that shows only items that are due within a certain number of days. For example, you can display all the items due within 7 days by filtering where the Due Date field is less than [Today]+7 and Due Date is greater than or equal to [Today]. You could also sort the view to show the items with earlier due dates closer to the top.
I'm looking for a way to build a table in a docusign template where the rows could be bound dynamically using the input data. For example, in the sample below the "Selected Options" is the table and the rows are dynamic user inputs :
**Selected Options**
2 bedroom
lake facing
non-smoking
Thanks
DocuSign does not support generic "tables" in the documents, so if you want to use a table it will have to be created at the document layer then uploaded into DocuSign.
One possible option is to create a the layout for a table in your document and leave spaces where the data will eventually go, then read or otherwise designate those locations on the document where the fields are, then finally you can place DocuSign tabs at those locations and that would in turn populate your table.
As Ergin says, DocuSign doesn't support dynamic creation of tables in a Document, such that the length (size) of the table will automatically vary according to how much data (i.e., how many rows) are specified. Your Create Envelope request specifies a (static) document, and you use DocuSign tabs to overlay data on top of that static document in specific locations.
That said, few options you might consider:
Create the table in your (static) document to contain the maximum number of columns/rows that it could ever possibly contain. Then, place tabs in every cell -- but in the Create Envelope request, only populate the tabs that correspond to the data the user provides. The down side of this approach would be that you could end up with a table that has several blank/empty rows, if the user doesn't specify much data.
OR
A more complex approach would be not define the Document in the Template itself, but rather, have the Create Envelope API request dynamically specify the Document, based on how much data the user provides. For example, if the table could contain between 1-3 rows, you could create 3 static documents -- the first with a one-row table, the second with a 2-row table, and the third with a 3-row table. Then, include logic in your code to determine how much data the user provides (1 row, 2 rows, or 3 rows), and specify the appropriate Document in the Create Envelope request. (Hint: you'd need to use 'Composite Templates' structure in the API request to accomplish this -- there's lots of info about that here on StackOverflow.) Biggest upside of this approach would be that the table in the document would always be the right size to exactly accommodate the user-provided data -- but obviously this approach could be challenging to implement and maintain if your document contains multiple tables and/or a large number of max potential rows in each table.
OR
Finally, in the same spirit as option #2 above -- if there's just a small number of variations of table size (for example: the table will always contain 1, 2, or 3 rows), you could simply create 3 Templates via the DocuSign web UI -- the first Template containing a Document with a one-row table, the second Template containing a Document with a 2-row table, and the third Template containing a Document with a 3-row table. Then, include logic in your code to dynamically choose the right template to use in the Create Envelope request, based upon how much data the user provides (1 row, 2 rows, or 3 rows).
Is there a way to create promotions in Netsuite 2016.1 so that items can have individually lowered prices? I know how to reduce items by percentages and how to set a flat price for all items, but I'm trying to allow individual items to have different temporary prices. Does Netsuite have this capability, or should I begin creating it via SuiteScript and custom records/fields?
Thanks!
Try the pricing groups feature of NetSuite. This lets you set a custom price for a set of items, which can then be assigned to various customers. This is primarily meant for negotiating prices with a large customer.
You might be able to use this feature to set temporary prices by switching the pricing group on and off for different customers with a script.
I am not aware of any way to temporarily set specific prices.
A thing I've done in the past was to create a set of custom fields and scripts that did the following for a Daily Specials program.
Take a group of products and copy their current on-line price to another field;
Update their online prices to a pre-determined value
assign them to a "Daily Specials" category.
set a custom checkbox field so that the item thumbnails could be easily bannered in a category list
A daily batch inspected a configuration table for that day's specials. It cleared all the current specials(prices back; remove from category; clear checkbox) and then assigned that day's specials.
this was driven by a table that allowed the product manager to schedule products based on seasonality and availability.
Using Business Objects Web Intelligence or Rich Client, is it possible to schedule a report to automatically run and export to Excel once for each parameter?
Background: I have a single report that needs to be saved to different Excel files once a month but I have a parameter on a "client" dimension which can contain 30+ values. Each value needs to generate its own Excel file. I would prefer to not run the report 30+ times each month.
Is there a way to schedule or change the WID query so that a separate file is generated for each parameter value? Or maybe an alternative idea for this manual process?
This can be done using a Publication with Dynamic Recipients.
You would need to create a second report that would produce a list of all values in your Client dimension. This report would then serve as the source of the Dynamic Recipients in the Publication. In the base report, you would remove the prompt on Client but make sure that Client is included in the report results. Then in the Publication, you would set Personalization such that a filter is automatically applied to the Client dimension based on the values from the second report.